Webhooks
Set webhook_url on a task to have outcomes pushed to you.
Payload
POST {webhook_url}
Content-Type: application/json
User-Agent: RingAHuman-Webhook/1
{
"event": "task.completed",
"task": {
"id": "task_9f2c1a…",
"status": "completed",
"external_ref": "crm_88213",
"outcome": {
"disposition": "booked",
"notes": "Spoke with Maria (office manager). Dr. Patel wants the report first.",
"meeting_at": "Thu Oct 9, 2:00pm CT",
"completed_at": "2026-10-06T15:11:43.000Z"
}
}
}
Delivery
Respond with any 2xx. Delivery is attempted once today and the result is recorded in the task's audit trail. For anything critical, also poll GET /api/tasks/{id}.
Tips
- Use
external_refto match the task to your CRM record. - Make your handler idempotent, keyed on
task.id.
Account-wide subscriptions
Instead of setting webhook_url on every task, subscribe once and receive every outcome for your account. This is what the Zapier and n8n apps use. You can also manage subscriptions in the dashboard under Integrations.
POST /api/hooks
Authorization: Bearer rah_live_…
{ "target_url": "https://example.com/ringahuman", "event": "task.completed" }
→ 201 { "id": "hook_…", "target_url": "https://example.com/ringahuman", "event": "task.completed" }
GET /api/hooks # list
DELETE /api/hooks/{id} # unsubscribe
Deliveries use the same payload as above. URLs must be HTTPS. If your endpoint answers 410 Gone, we remove the subscription.