Overview
PingBack provides three status-transition endpoints for conversations:- Resolve — marks a conversation as resolved and records the
resolved_attimestamp. - Close — marks a conversation as closed and records the
closed_attimestamp. - Assign — reassigns a conversation to a different agent.
PUT operations so you can model your support workflow precisely.
Resolve a conversation
Sets the conversation’sstatus to "resolved" and records resolved_at.
Method: PUT
URL: /api/v1/conversations/{conversation_id}/resolve
Headers
Path parameters
string (UUID)
required
The UUID of the conversation to resolve.
Response
string (ISO 8601)
Timestamp when the conversation was resolved.
If the conversation is already resolved, the endpoint returns
{"detail": "Already resolved"} with a 200 status.Example
Response example
Close a conversation
Sets the conversation’sstatus to "closed" and records closed_at.
Method: PUT
URL: /api/v1/conversations/{conversation_id}/close
Headers
Path parameters
string (UUID)
required
The UUID of the conversation to close.
Response
string (ISO 8601)
Timestamp when the conversation was closed.
If the conversation is already closed, the endpoint returns
{"detail": "Already closed"} with a 200 status.Example
Response example
Assign a conversation
Reassigns a conversation to a different agent. Method:PUT
URL: /api/v1/conversations/{conversation_id}/assign/{agent_id}
Headers
Path parameters
string (UUID)
required
The UUID of the conversation to reassign.
integer
required
The ID of the agent to assign the conversation to.
Response
integer
The ID of the newly assigned agent.