Create Provider
Providers
Create Provider
Create a new telephony provider configuration
POST
Create Provider
Documentation Index
Fetch the complete documentation index at: https://docs.unpod.dev/llms.txt
Use this file to discover all available pages before exploring further.
Create Provider Configuration
Create a new telephony provider configuration by linking your provider credentials (Account SID and Auth Token) to your organization. These configurations are used to connect telephony providers to bridges.Prerequisites: Make sure you have your API Token, Org-Handle, and telephony provider credentials ready. See Authentication for details.
Headers
| Name | Type | Required | Description |
|---|---|---|---|
| Authorization | string | Yes | API Key format: Token <token> |
| Org-Handle | string | Yes | Organization domain handle |
| Content-Type | string | Yes | application/json |
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
| Field | Type | Required | Description |
|---|---|---|---|
| provider | string | Yes | Provider identifier (slug or ID from Get Providers API) |
| account_sid | string | Yes | Provider Account SID / Account identifier |
| auth_token | string | Yes | Provider Auth Token / Secret key |
Response Fields
| Field | Type | Description |
|---|---|---|
| status_code | integer | HTTP status code |
| message | string | Response message |
| data | object | Created provider config details |
Provider Config Object Fields
| Field | Type | Description |
|---|---|---|
| id | integer | Unique provider configuration identifier |
| provider | string | Provider slug/identifier |
| account_sid | string | Account SID (auth_token is not returned) |
| created_at | string | Creation timestamp (ISO 8601) |
Common Error Codes
| Status Code | Description |
|---|---|
| 201 | Created - Provider configuration created |
| 400 | Bad Request - Invalid credentials or parameters |
| 401 | Unauthorized - Invalid or missing API token |
| 403 | Forbidden - Invalid organization handle |
| 409 | Conflict - Configuration already exists |
| 500 | Internal Server Error - Server-side error |
Code Examples
Best Practices
- Provider Slug: Use the
slugfrom the Get Telephony Providers endpoint to identify the provider - Credential Security: Never log or expose
auth_tokenvalues — treat them as secrets - Credential Rotation: Use the Update Provider endpoint to rotate credentials without deleting the configuration
- Configuration ID: Store the returned
idto reference this configuration when connecting to bridges - Error Handling: Handle 400 errors that indicate invalid credentials before they cause production issues
- Security: Keep API tokens secure and rotate them regularly
Authorizations
Format: Token
Headers
Organization domain handle
Example:
"unpod.tv"
Body
application/json
Response
Provider created