curl --request POST \
--url https://app.thinnest.ai/api/v1/conversations/{id}/status \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"status": "resolved"
}
'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({status: 'resolved'})
};
fetch('https://app.thinnest.ai/api/v1/conversations/{id}/status', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://app.thinnest.ai/api/v1/conversations/{id}/status"
payload = { "status": "resolved" }
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"status": "resolved",
"changed": true
}{
"error": "`status` is one of resolved, active, human_handling."
}{
"error": "Send a valid API key as `Authorization: Bearer <key>`."
}{
"error": "The shared inbox needs a paid plan. Switch to pay-as-you-go — there is no monthly fee — to move conversations."
}{
"error": "That conversation was not found."
}{
"error": "Over 240 requests a minute. Slow down and retry."
}Update Conversation Status
The inbox’s three moves: resolved marks it done and fires the conversation.resolved webhook, active hands it back to the agent, and human_handling takes it over so the agent stays quiet until it is handed back. An internal note records which API key made the change; the customer never sees it. changed: false means it was already in that state, and nothing was written or announced. The shared inbox needs a paid plan. A build key may do this.
curl --request POST \
--url https://app.thinnest.ai/api/v1/conversations/{id}/status \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"status": "resolved"
}
'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({status: 'resolved'})
};
fetch('https://app.thinnest.ai/api/v1/conversations/{id}/status', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://app.thinnest.ai/api/v1/conversations/{id}/status"
payload = { "status": "resolved" }
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"status": "resolved",
"changed": true
}{
"error": "`status` is one of resolved, active, human_handling."
}{
"error": "Send a valid API key as `Authorization: Bearer <key>`."
}{
"error": "The shared inbox needs a paid plan. Switch to pay-as-you-go — there is no monthly fee — to move conversations."
}{
"error": "That conversation was not found."
}{
"error": "Over 240 requests a minute. Slow down and retry."
}Authorizations
Your API key (ta_live_…) from Settings → API keys, sent as Authorization: Bearer <key>. Keep it on a server: it can message every customer you have. A key is full, build or read-only; a request its level does not allow is refused with 403.
Headers
Developers only: the customer workspace this request acts in — its org_… id from POST /customers. Leave it out to act in your own workspace.
"org_3fKq9TzQ1mN8vB2xR7cLpA"
Path Parameters
The conversation's id (conv_…).
Body
resolved: mark it done (fires conversation.resolved). active: hand it back to the agent. human_handling: take it over — the agent stays quiet until it is handed back.
resolved, active, human_handling