voice

Outbound Bridge Done

How the dial to the customer went -- the fact the callback policy runs on.

⛔THIS IS THE ONLY PLACE WE EVER LEARN WHETHER A CALLBACK REACHED ANYBODY. Plivo posts DialStatus here when the <Dial> ends: completed if the far end picked up, busy/no-answer/timeout/cancel/failed if it did not. Until this existed the system recorded that we DIALLED and nothing about whether it worked, so "we try up to three times, then we close it" had no third fact to count and no first fact to stop on.

Frederick, 2026-09-17: "within that one business day, we can try them up to three times ... we make one more call back attempt after that we close the call back attempt and you have to call us back to reset it."

⛔PUBLIC BY NECESSITY AND SIGNED BY DESIGN, like every other Plivo callback on this router: Plivo has no session, so the V3 HMAC is the authentication.

The XML hangs the account manager's leg up, which is what was going to happen anyway -- the customer's call is over.

post/api/voice/outbound/bridge-done/{ticket_id}

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/outbound/bridge-done/{ticket_id}
  • Auth: none declared

Path parameters

ticket_idstring uuid required

Response

Successful Response

unknown required

Changes

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