Skip to main content

POST /sms/conversations/{line}/{number}/reopen

Reopen a resolved conversation

Scopesms:write
Role permissionPhone numbers — line must be one of theirs
CostFree. Cannot reach the other party.

The missing half of resolve: a customer replies to a closed thread and it has to come back into the queue.

Idempotent, and a thread nobody ever resolved is already open — so this succeeds there too rather than 404ing.

Path parameters

NameTypeRequiredExampleDescription
linestringyes12125550188One of your account's numbers — the line the thread is on. Digits.
numberstringyes13475550123The other party's number. Digits.

Responses

200

The thread's state after the call.

FieldTypeDescription
linestringYour account number the thread is on, normalized.
numberstringThe other party's number, normalized.
resolvedbooleanThe thread's state after this call.
resolvedByintegerThe user credited, matching id in GET /users. Absent when an integration resolved it with no person named.
resolvedAtstring (RFC 3339)When, RFC 3339 UTC. Absent when not resolved.

Errors

StatusMeaning
400invalid_request — a missing or malformed field, an unknown enum value, or an unknown field in the body. Nothing was charged.
401unauthenticated — no credential, or one that is invalid, revoked or expired. The WWW-Authenticate header names the scope the endpoint wanted.
403Two different failures share this status, and the type tells them apart:
500internal_error — something failed on our side. For a send, nothing was charged, guaranteed, which is what makes a retry safe.

See Errors for the full catalog and what to do about each.

Example

curl -X POST 'https://api.account.telebroad.com/api/public/v1/sms/conversations/12125550188/13475550123/reopen' \
-H "Authorization: Bearer $TB_KEY"

Try it in the playground →