curl -X POST 'https://app.reddy.io/api/v1/call/stop' \
-H 'Authorization: Bearer your_api_key' \
-H 'Content-Type: application/json' \
-d '{
"conversation_id": "12345",
"agent_email": "agent@company.com",
"metadata": {
"call_duration": 300,
"resolution": "resolved"
}
}'
{
"success": true
}
Call Endpoints
Stop Call
Stops a call for a given conversation and agent.
POST
/
api
/
v1
/
call
/
stop
curl -X POST 'https://app.reddy.io/api/v1/call/stop' \
-H 'Authorization: Bearer your_api_key' \
-H 'Content-Type: application/json' \
-d '{
"conversation_id": "12345",
"agent_email": "agent@company.com",
"metadata": {
"call_duration": 300,
"resolution": "resolved"
}
}'
{
"success": true
}
Stops a call for a given conversation and agent.
Note that this can fail either from the user not matching an active Reddy user or from failing the lookup of the conversation. Conversations are unique by the user and conversation ID together.
This is a beta endpoint and not yet recommended for production use.
Request Body
string
required
The unique identifier for the conversation
string
required
The email address of the agent handling the call. Matched without regard to
capitalisation, so send it exactly as your directory stores it.
object
Additional metadata to associate with the call
Response
boolean
Indicates if the call was successfully stopped
Error Responses
object
More than one active user in your company has this
agent_email. Reddy will
not choose between them, so the request is rejected and nothing is recorded.
The body carries agent_email and conflicting_user_ids. Merge the duplicate
accounts, then resend.string
Error message when the user does not exist or conversation is not found
curl -X POST 'https://app.reddy.io/api/v1/call/stop' \
-H 'Authorization: Bearer your_api_key' \
-H 'Content-Type: application/json' \
-d '{
"conversation_id": "12345",
"agent_email": "agent@company.com",
"metadata": {
"call_duration": 300,
"resolution": "resolved"
}
}'
{
"success": true
}
Was this page helpful?