Skip to main content
GET
/
api
/
v2
/
platform
/
telephony
/
providers-configurations
/
{id}
Get Provider by ID
curl --request GET \
  --url http://localhost:3001/api/v2/platform/telephony/providers-configurations/{id}/ \
  --header 'Authorization: <api-key>' \
  --header 'Org-Handle: <org-handle>'
{
  "status_code": 200,
  "message": "Provider configuration fetched successfully.",
  "data": {
    "id": 42,
    "provider": "twilio",
    "account_sid": "ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    "created_at": "2026-02-07T10:00:00Z"
  }
}

{
  "status_code": 200,
  "message": "Provider configuration fetched successfully.",
  "data": {
    "id": 42,
    "provider": "twilio",
    "account_sid": "ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    "created_at": "2026-02-07T10:00:00Z"
  }
}

​
Get Provider Configuration by ID

Retrieve a specific telephony provider configuration by its unique integer identifier. Use this to inspect the details of a particular provider setup.
Prerequisites: Make sure you have your API Token and Org-Handle ready. See Authentication for details.

​
Path Parameters

NameTypeRequiredDescription
idintegerYesUnique identifier of the provider configuration
You can get the provider configuration id by hitting the Get All Providers API.

​
Headers

NameTypeRequiredDescription
AuthorizationstringYesAPI Key format: Token <token>
Org-HandlestringYesOrganization 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

FieldTypeDescription
status_codeintegerHTTP status code
messagestringResponse message
dataobjectProvider configuration details

​
Provider Config Object Fields

FieldTypeDescription
idintegerUnique provider configuration identifier
providerstringProvider slug/identifier
account_sidstringAccount SID for the provider
created_atstringConfiguration creation timestamp

​
Common Error Codes

Status CodeDescription
200Success - Configuration fetched successfully
401Unauthorized - Invalid or missing API token
403Forbidden - Invalid organization handle
404Not Found - Provider configuration not found
500Internal Server Error - Server-side error

​
Code Examples

const axios = require('axios');

const headers = {
  'Authorization': 'Token your-api-token',
  'Org-Handle': 'your-org-handle'
};

// Get provider configuration by ID
const getProviderById = async (id) => {
  const response = await axios.get(
    `https://unpod.dev/api/v2/platform/telephony/providers-configurations/${id}/`,
    { headers }
  );
  const config = response.data.data;
  console.log(`Provider: ${config.provider}`);
  console.log(`Account SID: ${config.account_sid}`);
  return config;
};

// Example usage
getProviderById(42);

​
Best Practices

  1. ID Lookup: Use Get All Providers to find IDs before fetching individual records
  2. Error Handling: Handle 404 responses when a configuration ID is no longer valid
  3. Security: auth_token is never returned — only account_sid is visible for security
  4. Org-Handle: Ensure the correct organization handle is used to access configurations within your org
  5. Validation: Use this endpoint to verify a provider configuration exists before connecting it to a bridge

Authorizations

​
Authorization
string
header
required

Format: Token

Headers

​
Org-Handle
string
required

Organization domain handle

Example:

"unpod"

Path Parameters

​
id
integer
required
Example:

1

Response

Provider configuration details