voice

Record Origination Failed

The browser telling us it could not place a call.

⛔THIS ROUTE EXISTS BECAUSE THE FACT NEVER REACHED US. On 2026-09-18 five of six agents could not place a call for a whole morning -- one shared Plivo endpoint, one call at a time -- and we learned about it from a Slack message. SoftphonePanel.tsx's onCallFailed knew the reason, told the agent, and told nobody else. There was no row to fail to write.

⛔ALWAYS 200, EVEN WHEN THE WRITE FAILS. This is reported by somebody who has just failed to reach a customer; the one thing worse than losing the record is turning it into a second visible failure. record swallows and logs, and the agent's own error message never depended on this landing.

post/api/voice/origination-failed

Request

  • Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.pigeonly.com/api/voice/origination-failed
  • Auth: none declared

Request body

reasonstring nullable
to_numberstring nullable
ticket_idstring uuid nullable

Response

Successful Response

object required

Changes

No recorded changes to this operation across all 1 revision of this API.