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

# Twilio - Trunking

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

## For AI agents

Programmatically remove an associated ip access control list from a trunk, associate an ip access control list with a trunk. Covers 24 operations with basic authentication.

## Scope

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

## Capabilities

- Remove an associated IP Access Control List from a Trunk
- Associate an IP Access Control List with a Trunk
- List all IP Access Control Lists for a Trunk
- Query and filter Twilio - Trunking records by parameters
- Monitor Twilio - Trunking operational status and events

## Use cases

### Developer Tools Operations

Use the Twilio - Trunking to perform developer tools operations programmatically. The API provides 24 endpoints covering core functionality including remove an associated ip access control list from a trunk, associate an ip access control list with a trunk, list all ip access control lists for a trunk.

Example prompt: Call DELETE /v1/Trunks/{TrunkSid}/IpAccessControlLists/{Sid} to remove an associated ip access control list from a trunk

### Automated TrunkingV1CredentialList Management

Automate trunkingv1credentiallist operations by combining multiple Twilio - Trunking endpoints. Agents can associate an ip access control list with a trunk and then list all ip access control lists for a trunk in a single workflow.

Example prompt: Call POST /v1/Trunks/{TrunkSid}/IpAccessControlLists to associate an ip access control list with a trunk, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Twilio - Trunking 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 'remove an associated ip access control list from a trunk', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| DELETE | /v1/Trunks/{TrunkSid}/IpAccessControlLists/{Sid} | Remove an associated IP Access Control List from a Trunk |
| POST | /v1/Trunks/{TrunkSid}/IpAccessControlLists | Associate an IP Access Control List with a Trunk |
| GET | /v1/Trunks/{TrunkSid}/IpAccessControlLists | List all IP Access Control Lists for a Trunk |

## Key resources

- **TrunkingV1CredentialList** — Operations related to TrunkingV1CredentialList
- **TrunkingV1IpAccessControlList** — Operations related to TrunkingV1IpAccessControlList
- **TrunkingV1OriginationUrl** — Operations related to TrunkingV1OriginationUrl
- **TrunkingV1PhoneNumber** — Operations related to TrunkingV1PhoneNumber
- **TrunkingV1Recording** — Operations related to TrunkingV1Recording

## Why Jentic

- **Setup:** Wiring Twilio Trunking by hand means setting up HTTP basic auth with your account SID and auth token against the trunking.twilio.com host and handling retries yourself. Through Jentic you install once, import Twilio Trunking from the API Directory, store the account SID and auth token once, and your agent calls it.
- **Permission scoping:** Twilio Trunking puts the trunk Sid in the URL path (/v1/Trunks/{TrunkSid}/IpAccessControlLists/{Sid}), so a rule can pin your agent to one trunk. You choose the operations it may call, so destructive ones like removing an IP access control list 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 'list IP access control lists for a trunk' or 'attach an IP access control list', and Jentic returns the matching Twilio Trunking operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

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

The Twilio - Trunking 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 remove an associated ip access control list from a trunk with the Twilio - Trunking?

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

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

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 remove an associated ip access control list from a trunk through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'remove an associated ip access control list from a trunk'. Jentic returns the matching Twilio - Trunking operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The Twilio - Trunking exposes 24 endpoints covering trunkingv1credentiallist, trunkingv1ipaccesscontrollist, trunkingv1originationurl operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Twilio Trunking operations the agent may call, so destructive ones like DELETE /v1/Trunks/{TrunkSid}/IpAccessControlLists/{Sid} stay unavailable unless you add them. Since the trunk Sid sits in the URL path, a rule can pin the agent to a single trunk while still letting it list or attach IP access control lists. The Twilio account SID and auth token are stored encrypted by your own instance and injected only at execution time, so the agent never sees the raw secrets.