Get All Providers
Providers
Get All Providers
Retrieve all configured telephony provider configurations
GET
Get All 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 All Provider Configurations
Retrieve all telephony provider configurations that have been set up for your organization. Each configuration represents a set of credentials (account SID) linked to a specific telephony provider.Prerequisites: Make sure you have your API Token and Org-Handle 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 |
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 configuration objects |
Provider Config Object Fields
| Field | Type | Description |
|---|---|---|
| id | integer | Unique provider configuration identifier |
| provider | string | Provider slug/identifier |
| account_sid | string | Account SID for the provider |
| created_at | string | Configuration creation timestamp |
Common Error Codes
| Status Code | Description |
|---|---|
| 200 | Success - Configurations 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
- Configuration ID: Note each configuration
id— it is used when connecting a provider to a bridge - Multiple Providers: You can have configurations for multiple providers to support different regions
- Security:
auth_tokenis never returned in responses for security — onlyaccount_sidis shown - Error Handling: Always handle potential errors and edge cases
- Regular Auditing: Periodically review and remove unused provider configurations