canonical: https://jentic.com/apis/twilio.com/twilio---voice

# Twilio - Voice

This is the public Twilio REST API. The API exposes 32 endpoints secured with basic authentication.

## For AI agents

Programmatically delete an archived call record from bulk export. note: this does not also delete, retrieve voice dialing country permissions identified by the given iso country c. Covers 32 operations with basic authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Delete an archived call record from Bulk Export. Note: this does not also delete
- Retrieve voice dialing country permissions identified by the given ISO country c
- Create a bulk update request to change voice dialing country permissions of one
- Fetch the high-risk special services prefixes from the country resource correspo
- Update voice dialing permissions inheritance for the sub-account

## Use cases

### Communications Operations

Use the Twilio - Voice to perform communications operations programmatically. The API provides 32 endpoints covering core functionality including delete an archived call record from bulk export. note: this does not also delete, retrieve voice dialing country permissions identified by the given iso country c, retrieve all voice dialing country permissions for this account.

Example prompt: Call DELETE /v1/Archives/{Date}/Calls/{Sid} to delete an archived call record from bulk export. note: this does not also delete

### Automated VoiceV1ArchivedCall Management

Automate voicev1archivedcall operations by combining multiple Twilio - Voice endpoints. Agents can retrieve voice dialing country permissions identified by the given iso country c and then retrieve all voice dialing country permissions for this account in a single workflow.

Example prompt: Call GET /v1/DialingPermissions/Countries/{IsoCode} to retrieve voice dialing country permissions identified by the given iso country c, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Twilio - Voice endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Example prompt: Search Jentic for 'delete an archived call record from bulk export. note: this does not also delete', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| DELETE | /v1/Archives/{Date}/Calls/{Sid} | Delete an archived call record from Bulk Export. Note: this does not also delete |
| GET | /v1/DialingPermissions/Countries/{IsoCode} | Retrieve voice dialing country permissions identified by the given ISO country c |
| GET | /v1/DialingPermissions/Countries | Retrieve all voice dialing country permissions for this account |
| POST | /v1/DialingPermissions/BulkCountryUpdates | Create a bulk update request to change voice dialing country permissions of one |
| GET | /v1/DialingPermissions/Countries/{IsoCode}/HighRiskSpecialPrefixes | Fetch the high-risk special services prefixes from the country resource correspo |
| POST | /v1/Settings | Update voice dialing permissions inheritance for the sub-account |
| GET | /v1/Settings | Retrieve voice dialing permissions inheritance for the sub-account |

## Key resources

- **VoiceV1ArchivedCall** — Operations related to VoiceV1ArchivedCall
- **VoiceV1BulkCountryUpdate** — Operations related to VoiceV1BulkCountryUpdate
- **VoiceV1ByocTrunk** — Operations related to VoiceV1ByocTrunk
- **VoiceV1ConnectionPolicy** — Operations related to VoiceV1ConnectionPolicy
- **VoiceV1ConnectionPolicyTarget** — Operations related to VoiceV1ConnectionPolicyTarget

## Why Jentic

- **Setup:** Wiring Twilio Voice by hand means setting up HTTP basic auth with your account SID and auth token against the voice.twilio.com host and handling retries yourself. Through Jentic you install once, import Twilio Voice from the API Directory, store the account SID and auth token once, and your agent calls it.
- **Permission scoping:** Twilio Voice puts the archived call and dialing permission country in the URL path (/v1/DialingPermissions/Countries/{IsoCode}), so a rule can pin your agent to reads on a given country. You choose the operations it may call, so destructive ones like deleting an archived call record or bulk country updates are not included unless you add them.
- **Credential handling:** Your Twilio account SID and auth token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'read dialing permissions for a country' or 'update voice settings', and Jentic returns the matching Twilio Voice operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Sendgrid** — Alternative communications API
- **Pusher** — Alternative communications API

## FAQ

### What authentication does the Twilio - Voice use?

The Twilio - Voice uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I delete an archived call record from bulk export. note: this does not also delete with the Twilio - Voice?

Yes. Use the DELETE /v1/Archives/{Date}/Calls/{Sid} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Twilio - Voice?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I delete an archived call record from bulk export. note: this does not also delete through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'delete an archived call record from bulk export. note: this does not also delete'. Jentic returns the matching Twilio - Voice operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Twilio - Voice have?

The Twilio - Voice exposes 32 endpoints covering voicev1archivedcall, voicev1bulkcountryupdate, voicev1byoctrunk operations.

### Can I limit what my agent is allowed to do with the Twilio Voice API?

Yes. Because Jentic One is self-hosted, you decide which Twilio Voice operations your agent may call, and your own rules are enforced at execution time. Since the country is carried in the URL path, such as GET /v1/DialingPermissions/Countries/{IsoCode}, you can pin the agent to reads of dialing permissions for a given country and leave destructive operations like DELETE /v1/Archives/{Date}/Calls/{Sid} or bulk country updates out of scope. Your Twilio account SID and auth token stay encrypted in your own instance and are injected only for the calls you have allowed.