Get the signed Twilio inbound-Voice webhook URL for a verified BYO account
const url = 'https://api.vocapable.com/v1/telephony-accounts/example/inbound-voice-webhook';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.vocapable.com/v1/telephony-accounts/example/inbound-voice-webhook \ --header 'Authorization: Bearer <token>'Return the account-level Voice URL a customer copies into Twilio’s number config.
The URL remains useless without Twilio’s account-specific request signature, and every accepted callback re-resolves its signed destination against an active carrier-owned voice number with a selected published agent. Managed or unverified accounts cannot publish an inbound route, so they never become a back door around the BYO verification boundary.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Responses
Section titled “Responses”Successful Response
The exact signed Twilio Voice URL for one eligible BYO account.
It is publishable configuration, not a bearer capability: Twilio still signs every request with the account’s vaulted auth token, and the signed destination is then resolved against one active carrier-confirmed voice number with an explicit receiving agent. The route returns no useful response until all of those server-side checks pass.
Examplegenerated
{ "url": "example", "status_callback_url": "example"}Validation Error
object
object
object
Examplegenerated
{ "detail": [ { "loc": [ "example" ], "msg": "example", "type": "example", "input": "example", "ctx": {} } ]}