Call Routing via APIs

Publisher

Dialpad

URL

https://developers.dialpad.com/docs/call-routing-via-apis.md

Published

2025-09-18

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

Dialpad website terms; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• A Dialpad API call router's endpoint may answer with route (to a Dialpad user, department, call center or office), forward (to an E.164 number), ask (TTS prompt with DTMF collection) or end. in context
• A Dialpad API call router is automatically disabled if its endpoint takes more than 5 seconds to respond or fails more than 10 times in an hour, after which calls go to the configured default target. in context
• When a call router is configured with a secret, Dialpad sends a signed JWT payload to the routing endpoint instead of raw JSON. in context
• Given the 5 second timeout and automatic disabling, any production Dialpad API call router should have a default target configured and monitoring that detects when it is disabled. inferred in context

Cite this source record

APA

WarmTransfer. (2025, September 18). Call Routing via APIs. WarmTransfer. https://warmtransfer.net/knowledge/sources/dialpad-dev-call-routing-apis

BibTeX

@misc{warmtransfer-dialpad-dev-call-routing-apis,
  title  = {Call Routing via APIs},
  author = {{WarmTransfer}},
  year   = {2025},
  url    = {https://warmtransfer.net/knowledge/sources/dialpad-dev-call-routing-apis},
  note   = {Dialpad, accessed 2026-09-24}
}