Skip to main content
POST
Connect Provider to Bridge

Connect Provider to Bridge

Connect a telephony provider configuration to a specific bridge, linking a phone number to the bridge for call routing. This enables inbound and outbound calls through the connected provider.
Prerequisites: Make sure you have your API Token, Org-Handle, a configured Bridge, and a Provider Configuration ready. See Authentication for details.
The provider_config_id must be a valid provider configuration already created for your organization. You can only use a phone_number that is linked to the provider account.

Path Parameters

You can get the bridge slug by hitting the Get All Bridges API. The slug field in the response is your Bridge Slug.

Headers

You can get the Org-Handle by hitting the Get All Organizations API. The domain_handle field in the response is your Org-Handle.

Request Body

Response Fields

Data Object Fields

Common Error Codes

Code Examples

Best Practices

  1. Provider Config ID: Get the correct provider_config_id from Get All Providers before connecting
  2. Phone Number Format: Use E.164 format (e.g., +1234567890) for phone numbers
  3. Verify Bridge: Confirm the bridge exists using Get Bridge by Slug before connecting
  4. One Provider per Bridge: A bridge typically connects to one provider - verify current state before re-connecting
  5. Error Handling: Handle 400 errors that may indicate an invalid phone number or provider config
  6. Security: Keep API tokens secure and rotate them regularly

Authorizations

Authorization
string
header
required

Format: Token

Headers

Org-Handle
string
required

Organization domain handle

Example:

"unpod.tv"

Path Parameters

slug
string
required
Example:

"sales-bridge-001"

Body

application/json
provider_config_id
integer
required
Example:

42

phone_number
string
required
Example:

"+1234567890"

Response

Provider connected to bridge