Account
Paste a Retell API key to read your own calls, agents and numbers (read scope is enough). Or load the synthetic sample account.
Why calls ended
Every disconnection_reason in the window, grouped by who owns the fix.
| Reason | Class | Calls | Fix owner | First check |
|---|
Calls
Click a call for the latency breakdown, a diagnosis, and a reply you can send.
| Start (UTC) | Agent | Type | Secs | Ended | e2e p50/p90 | Slowest part |
|---|
Live webhook inbox
Set this as an agent's webhook URL, place a test call, and watch call_started / call_ended / call_analyzed arrive. Deliveries are kept 24 hours and each one is checked against X-Retell-Signature with the key above.
No Retell account? The two test buttons sign a sample call_ended body with the key field (or key_demo_not_a_real_key if empty) using the SDK's scheme, so you can see a pass and a failure end to end.
| Received | Event | Call | Source | Signature |
|---|
Check a signature by hand
For a customer's failing endpoint: paste the exact raw body they received, the header, and the webhook key. The checker says which part is wrong.
Custom LLM WebSocket probe
Connects to a customer's LLM server the way Retell does, sends a Mandarin turn, and grades what comes back against the protocol. Runs from Cloudflare's edge, so it sees the public internet the way Retell's servers do.
Raw frames
Agent audit
Language, voice, engine and webhook per agent, checked against Retell's language-support tables for a Mandarin deployment.
| Agent | Language | Voice | Engine | Findings |
|---|
Numbers
| Number | Type | Bound agents | Findings |
|---|
E.164 checker
invalid_destination is usually a formatting problem in the customer's CRM. Paste numbers, one per line.
| Input | Market | E.164 | Issues and notes |
|---|