API reference · Outreach
Chat
Post a reply into a live website chat conversation. The visitor sees it in the chat widget right away, and your team sees it in the shared inbox marked as an automation reply.
Send a reply
POST /chat/public/reply with API keys, or OAuth with the chat:write scope.
curl -X POST https://api-v2.dropcowboy.com/chat/public/reply \
-H "x-key: $DC_KEY" -H "x-secret: $DC_SECRET" \
-H "Content-Type: application/json" \
-d '{
"conversation_id": "2b7d9f1a-4c6e-4e8a-b0d2-6f8a1c3e5b79",
"message": "Thanks for reaching out! A teammate will follow up within the hour.",
"sender_name": "Example Dental"
}'
| Field | Required | Notes |
|---|---|---|
conversation_id |
Yes | From the chat automation triggers, such as "Chat Received" |
message |
Yes, or body |
Reply text. body is accepted as an alias and wins if both are sent |
sender_name |
No | Name the visitor sees. Defaults to Automation |
metadata |
No | Object stored with the message |
The response is {"data": {"message_id": "...", "conversation_id": "..."}, "meta": {...}}.
Each call posts a new message. There is no Idempotency-Key on this route, so
retrying after a success sends the reply twice.
Use GET /chat/public/sites to list your chat sites.
Errors
| Status | When |
|---|---|
400 |
conversation_id or the message is missing |
402 |
Your most recent payment failed (payment-required) |
403 |
Missing chat:write scope, the plan has no chat seat (addon_not_enabled), or the account is inactive |
404 |
No conversation with that id in your account |
Errors are problem details. The 400 has type .../errors/validation-error,
the 404 has .../errors/not-found, and any other failure has
.../errors/server-error. See Errors and limits.