Developers
Webhooks
Aurtio sends a signed POST to your server when a call ends, a lead is noted, a booking is made, or a call summary is ready. Send them to your own code, or to n8n, Zapier or Make.
#Set up an endpoint
- In the app, open Integrations and press Connect on the n8n, Make, Zapier or HTTP tile. Only the workspace owner can.
- Enter your Destination URL (https): an HTTPS address reachable from the internet.
- Under Send these events, tick After every call, New lead captured, Booking made and/or Call summary ready, then press Connect.
- Copy the Signing secret (
whsec_…). It is shown once. - Press Send a test delivery.
You can also manage endpoints with the API: Webhook endpoints. There, an empty events list means all events.
#Events
| Event | When | What data holds |
|---|---|---|
call.ended | A customer call ends | The call's id, length, cost and turn count. No transcript: fetch it with GET /v1/calls/{id}. |
lead.captured | Your employee notes a lead | Name, phone and what they need. Also sent when the call summary finds a lead the call missed. |
booking.created | Your employee notes a booking | Name, the time in the caller's words, and the purpose. Also sent when the summary finds one. |
call.summary | The call's summary is written | A 1–2 line summary, the outcome, and the details it noted. |
test.ping | You press Test | A short note. Always sent to that endpoint, whatever events it chose. |
#Payloads
Every body has the same four keys. id is the delivery id: it stays the same if a delivery is retried or re-sent, so you can use it to ignore duplicates.
{
"id": "6f1c…",
"event": "call.ended",
"created_at": "2026-11-08T10:30:00.512000+00:00",
"data": {
"id": "<call id>",
"agent_id": "<employee id>",
"agent_name": "Front Desk",
"room": "call-…",
"direction": "inbound",
"caller": null,
"duration_sec": 42.0,
"cost_inr": 1.4,
"turns": 6
}
}{
"id": "8a02…",
"event": "lead.captured",
"created_at": "2026-11-08T10:29:41.120000+00:00",
"data": {
"id": "<lead id>",
"agent_id": "<employee id>",
"agent_name": "Front Desk",
"call_room": "call-…",
"name": "Ravi",
"phone": "98765…",
"requirement": "dental appointment"
}
}{
"id": "b913…",
"event": "booking.created",
"created_at": "2026-11-08T10:29:55.004000+00:00",
"data": {
"id": "<booking id>",
"agent_id": "<employee id>",
"agent_name": "Front Desk",
"call_room": "call-…",
"name": "Ravi",
"when_text": "kal shaam 5 baje",
"purpose": "consultation"
}
}{
"id": "c4d7…",
"event": "call.summary",
"created_at": "2026-11-08T10:31:12.300000+00:00",
"data": {
"call_id": "<call id>",
"agent_id": "<employee id>",
"room": "call-…",
"summary": "…",
"disposition": "booking",
"fields": { "name": "Ravi", "phone": null, "appointment_time": "kal 5pm" },
"duration_sec": 192.0,
"cost_inr": 3.2
}
}dispositionis one oflead,booking,inquiry,no_outcomeorother.fieldsholds the details your employee is set to note; a detail the caller didn't give isnull.- A lead or booking found after the call carries
"source": "post_call". - For calls from your website button,
directionisinboundandcallerisnull: there is no phone number.
#Headers
| Header | Example | What it is |
|---|---|---|
X-Aurtio-Event | lead.captured | The event name, the same as the body's event. |
X-Aurtio-Delivery | 8a02… | The delivery id, the same as the body's id. |
X-Aurtio-Signature | t=…,v1=… | The time it was signed and the HMAC. See below. |
User-Agent | Aurtio-Webhooks/1.0 | Followed by (+https://aurtio.ai). |
Content-Type | application/json | The body is JSON. |
#Verify the signature
The signature header looks like t=1762597800,v1=5f2b…. t is a Unix time in seconds, and v1 is the hex HMAC-SHA256 of {t}.{raw body} with your whsec_ secret as the key.
- Read the body as raw text, before you parse the JSON.
- Reject the request if
tis more than 300 seconds from your clock. This stops replays. - Compute the HMAC and compare it with
v1in constant time.
import crypto from "node:crypto";
export function verify(secret, raw, header) {
const p = Object.fromEntries(header.split(",").map((kv) => kv.split("=")));
if (Math.abs(Date.now() / 1000 - Number(p.t)) > 300) return false;
const mac = crypto.createHmac("sha256", secret).update(`${p.t}.${raw}`).digest("hex");
return typeof p.v1 === "string" && p.v1.length === mac.length &&
crypto.timingSafeEqual(Buffer.from(mac), Buffer.from(p.v1));
}import hashlib, hmac, time
def verify(secret, raw, header):
p = dict(kv.split("=", 1) for kv in header.split(","))
if abs(time.time() - int(p["t"])) > 300:
return False
mac = hmac.new(secret.encode(), f"{p['t']}.{raw}".encode(), hashlib.sha256).hexdigest()
return hmac.compare_digest(mac, p.get("v1", ""))Answer with any 2xx status as soon as you have checked the signature, then do the slow work. A slow reply counts as a failure.
#Retries and timeouts
- Each attempt waits at most 5 seconds for your reply. Any 2xx status counts as delivered.
- Redirects are not followed: a 3xx counts as a failure.
- A failed delivery is tried 5 times in all. The waits between tries are 30 seconds, 2 minutes, 8 minutes and 32 minutes. After the fifth failure it is marked failed.
- Addresses that resolve to private or internal networks are refused, and are not retried.
#Test and re-send
On the Integrations page, each endpoint has Test, which sends a test.ping, and Recent deliveries, which lists each delivery as Delivered, Failed or Sending. Press Send again to re-send one; the delivery id stays the same. If the secret leaks, press Rotate secret, then Confirm rotate: the new secret works at once, and the endpoint keeps its id.
{
"id": "…",
"event": "test.ping",
"created_at": "…",
"data": { "note": "Aurtio webhook test — your endpoint works!" }
}