/v1/conversations/{conversation_id}/closebetaClose a conversation
- Needs
- Manage conversations: notes, assign, close, tags, reminders
(inbox:write) - Plan
- Any plan with API access
- Limits
- 60 a minute per key
- Dry run
- Yes — every check runs with ?dry_run=true, nothing changes
- Confirm
- Header
Api-Confirm: close - Undo
- Reopen it with Reopen a conversation (a new episode starts; the automations that ran on close are not undone).
Closes a conversation with a closing reason: it ends the current episode, stops its SLA clock and fires conversation.closed automations and webhooks. Optionally adds an internal note first.
Send Api-Confirm: close. Closing one that is already closed changes nothing (changed: false). A new message from the customer reopens it.
Try it
Protects against doing it twice if you retry: a retry with the same key gets the first answer back instead of running again.
Code and response
curl -X POST 'https://mcp.wa-api.cloud/v1/conversations/77410/close?dry_run=true' \
-H "Authorization: Bearer $API_KEY" \
-H 'Content-Type: application/json' \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"closed_reason_id": "3",
"note": "Order shipped; the customer confirmed."
}'The code reads your key from $API_KEY.
Parameters
| Field | Type | What it is |
|---|---|---|
| conversation_idrequired | string · path | The conversation id.pattern ^\d{1,19}$Signed in? Pick one from your data with “My data”. |
Body
| Field | Type | What it is |
|---|---|---|
| closed_reason_idrequired | string | The id of one of the workspace's closing reasons (set up in the inbox settings).pattern ^\d{1,19}$ |
| note | string | An internal note to add before closing (never shown to the customer).1–5000 characters |
Headers
| Field | Type | What it is |
|---|---|---|
| Authorizationrequired | header | Bearer $API_KEY — your API key. |
| Api-Version | header | The API version to use, e.g. 2026-10-01. Default: the version your key is pinned to.one of: 2026-10-01 · pattern ^\d{4}-\d{2}-\d{2}$ |
| Idempotency-Key | header | Any unique string (8–128 characters). A retry with the same key returns the first answer instead of running twice. Kept 24 hours.pattern ^[A-Za-z0-9._:-]+$ · 8–128 characters |
| Api-Confirmrequired | header | Type the operation's verb (e.g. delete, submit) to confirm a change that cannot be undone or that WhatsApp or your customers see. Not needed with dry_run=true. |
Response 200
The conversation's new state.
| Field | Type | What it is |
|---|---|---|
| conversationrequired | object | |
| idrequired | string | |
| staterequired | string or null | |
| assignee_staff_idrequired | string or null | |
| team_idrequired | string or null | |
| tagsrequired | array of object | |
| idrequired | string | |
| namerequired | string | |
| changedrequired | boolean | |
| note_idrequired | string or null | |
| dry_run | boolean | true when this was a dry run: every check ran and nothing changed. |
Errors
Errors are application/problem+json. Branch on code.
| Status | Code | When |
|---|---|---|
| 400 | invalid_input | A field is missing or has the wrong format. |
| 401 | unauthenticated | The Authorization header is missing, the key is unknown, expired or revoked. |
| 403 | entitlement_required | The workspace's plan does not include API access ( |
| 403 | insufficient_scope | The key does not have the permission this operation needs. |
| 404 | not_found | No conversation with this id. |
| 409 | conflict | Also returned while a request with the same Idempotency-Key is still running. |
| 428 | confirm_required | Send the header |
| 429 | rate_limited | The key or workspace went over its rate limit. Wait for |
| 503 | upstream_unavailable | A service behind the API is briefly unavailable. Safe to retry with backoff. |
| 504 | timeout | The change did not finish in time. Retry with the same Idempotency-Key: it never runs twice. |
Examples
Close a resolved conversation
Request body
{
"closed_reason_id": "3",
"note": "Order shipped; the customer confirmed."
}Response 200
{
"conversation": {
"id": "77410",
"state": "closed",
"assignee_staff_id": "1203",
"team_id": null,
"tags": [
{
"id": "4",
"name": "new-lead"
}
]
},
"changed": true,
"note_id": "90332"
}Webhook events
These events can fire after this call. Subscribe an endpoint to hear about them.
Operation path
The same operation is also at POST /v1/ops/inbox_close_conversation, with every field in the JSON body.