Get Telephony Providers
Providers
Get Telephony Providers
Retrieve a list of all available telephony providers in the system
GET
Get Telephony Providers
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.
Get Telephony Providers
Retrieve a list of all available telephony providers in the system. These are the supported providers that you can configure credentials for using the Provider Configurations endpoints.Prerequisites: Make sure you have your API Token and Org-Handle ready. See Authentication for details.
Get Telephony Providers
Retrieve all supported telephony providers available for configuration.Headers
| Name | Type | Required | Description |
|---|---|---|---|
| Authorization | string | Yes | API Key format: Token <token> |
| Org-Handle | string | Yes | Organization domain handle |
You can get the
Org-Handle by hitting the Get All Organizations API. The domain_handle field in the response is your Org-Handle.Response Fields
| Field | Type | Description |
|---|---|---|
| status_code | integer | HTTP status code |
| message | string | Response message |
| data | array | Array of provider objects |
Provider Object Fields
| Field | Type | Description |
|---|---|---|
| id | integer | Provider unique identifier |
| name | string | Provider display name |
| slug | string | URL-friendly provider identifier used in config API |
Common Error Codes
| Status Code | Description |
|---|---|
| 200 | Success - Providers fetched successfully |
| 401 | Unauthorized - Invalid or missing API token |
| 403 | Forbidden - Invalid organization handle |
| 500 | Internal Server Error - Server-side error |
Code Examples
Best Practices
- Provider ID: Use the
idfield when creating provider configurations via the Create Provider endpoint - Provider Selection: Choose the provider that best suits your region and call volume requirements
- Caching: Cache the providers list locally since it changes infrequently
- Error Handling: Always handle potential errors and implement retry logic
- Security: Keep API tokens secure and rotate them regularly