Skip to main content
Choose the import variant that matches the number or trunk you control. The current API accepts Twilio, Exotel, and SIP configuration, but import does not authenticate the provider account, provision a number, or verify live calling.

​
Choose an import variant

Use the full Import phone number schema for optional fields and exact request types. An optional agent_id must identify an agent available in the workspace.

​
Twilio preparation

The sid field accepts an Account SID or API Key SID. Pair it with the corresponding Account Auth Token or API Key Secret. The current validator requires enable_sms: false; its default value of true is rejected. It also rejects account_auth_token until a secure webhook-signature credential handoff is available. These restrictions mean you must not describe an import as enabling SMS or completing an API-key-based inbound webhook setup. For carrier-side trunk requirements, use Twilio’s official SIP documentation.

​
Exotel preparation

Collect the account SID and API credentials from the account’s API settings. Confirm the region-specific API host and the intended app ID. Exotel’s getting-started guide explains where these account details originate. An Exotel record in Threetone does not prove that an applet, callback, or outbound runtime has been configured.

​
SIP preparation

Use the SIP trunk guide to review routing direction, address restrictions, transport, media policy, and credentials with the trunk operator.

​
Verify the result

1

Import only the intended configuration

Submit the appropriate variant from a trusted server or authorized dashboard workflow. Keep credentials out of screenshots and issue reports.
2

Inspect the saved record

Read the returned phone-number ID. Confirm the provider, routing identity, assignment, and configuration. Import stores redacted credential metadata, so it is not proof of a usable runtime secret.
3

Review runtime readiness

Verify credential handoff, the provider-specific route, and the selected executable agent version separately. The general outbound route requires managed PSTN with Twilio fulfillment; an Exotel or SIP import does not satisfy that requirement.

​
Frequently asked questions

Check that enable_sms is explicitly false and account_auth_token is omitted. The current implementation rejects both SMS enablement and the separate webhook credential field.
Do not assume that it does. Deletion follows a cancellation workflow with provider-specific requirements. Verify the final provider state separately.