Send human agent response | Atlas

Sends a manual reply from a live agent. sessionId must be the contact’s current session and that session must be in a human-handoff state (enable it first via the human-handoff endpoint). Targeting a stale, closed, or non-handoff session returns 400 {"error":{"message":"Human handoff is not enabled for this campaign","code":"BAD_REQUEST"}} — despite the wording, the cause is the session, not a campaign-level setting.

Sends a manual reply from a live agent. `sessionId` must be the contact's **current** session and that session must be in a human-handoff state (enable it first via the human-handoff endpoint). Targeting a stale, closed, or non-handoff session returns `400 {"error":{"message":"Human handoff is not enabled for this campaign","code":"BAD_REQUEST"}}` — despite the wording, the cause is the session, not a campaign-level setting.

Authentication

api-keystring

Your Atlas API key. Get it from the Atlas Portal under Settings > API Keys.

Path parameters

campaignIdstringRequired

Request

This endpoint expects an object.

sessionIdstringRequired

messagestringRequired

agentIdstringOptional

attachmentslist of stringsOptional

Response

Response sent

Errors

400

Bad Request Error

500

Internal Server Error

$	curl -X POST https://api.youratlas.com/v1/api/campaign-chat/campaignId/send-human-response \
>	-H "api-key: <apiKey>" \
>	-H "Content-Type: application/json" \
>	-d '{
>	"sessionId": "a1b2c3d4-e5f6-7890-ab12-cd34ef567890",
>	"message": "Hello, how can I assist you with your order today?"
>	}'