Overview

Configure telephony providers and manage phone numbers

A telephony configuration binds an organization to a telephony provider (Twilio, Vonage, Plivo, Telnyx, etc.) along with the credentials needed to place and receive calls. Each configuration owns a set of phone numbers; campaigns and inbound routing pin to a specific configuration.

One configuration in your organization can be marked as the default outbound — campaigns and ad-hoc calls that omit telephony_configuration_id fall back to it.

MethodEndpointQuick Link
GET/organizations/telephony-providers/metadataList supported providers
GET/organizations/telephony-configsList configurations
POST/organizations/telephony-configsCreate a configuration
GET/organizations/telephony-configs/{config_id}Get a configuration
PUT/organizations/telephony-configs/{config_id}Update a configuration
DELETE/organizations/telephony-configs/{config_id}Delete a configuration
POST/organizations/telephony-configs/{config_id}/set-default-outboundSet as default outbound

Phone numbers#

Phone numbers are nested under a configuration:

MethodEndpointQuick Link
GET/organizations/telephony-configs/{config_id}/phone-numbersList phone numbers
POST/organizations/telephony-configs/{config_id}/phone-numbersAdd a phone number
GET/organizations/telephony-configs/{config_id}/phone-numbers/{phone_number_id}Get a phone number
PUT/organizations/telephony-configs/{config_id}/phone-numbers/{phone_number_id}Update a phone number
DELETE/organizations/telephony-configs/{config_id}/phone-numbers/{phone_number_id}Delete a phone number
POST/organizations/telephony-configs/{config_id}/phone-numbers/{phone_number_id}/set-default-callerSet as default caller

Sensitive credentials#

Provider credentials (API keys, auth tokens, etc.) are masked in GET responses. When updating a configuration, you can re-submit the masked value as-is — Paladin detects the mask and preserves the original secret.

How to use this reference#

Use this page as the entry point for the related API endpoints. Open the endpoint-specific page when you need the exact method, path, request body, response schema, and OpenAPI details.

Implementation checklist#

  1. Start with the overview table to choose the correct endpoint.
  2. Confirm authentication and organization scope before calling the endpoint from code.
  3. Test with a small request first, then inspect the response and error handling path.