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

# Twilio - Proxy

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

## For AI agents

Programmatically retrieve a list of interactions for a given [session](https://www.twilio.com/doc, delete a specific interaction.. Covers 30 operations with basic authentication.

## Scope

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

## Capabilities

- Retrieve a list of Interactions for a given [Session](https://www.twilio.com/doc
- Delete a specific Interaction.
- Create a new message Interaction to send directly from your system to one [Parti
- Fetch a specific Participant.
- Add a new Participant to the Session

## Use cases

### Developer Tools Operations

Use the Twilio - Proxy to perform developer tools operations programmatically. The API provides 30 endpoints covering core functionality including retrieve a list of interactions for a given [session](https://www.twilio.com/doc, delete a specific interaction., retrieve a list of all interactions for a session. a maximum of 100 records will.

Example prompt: Call GET /v1/Services/{ServiceSid}/Sessions/{SessionSid}/Interactions/{Sid} to retrieve a list of interactions for a given [session](https://www.twilio.com/doc

### Automated ProxyV1Index Management

Automate proxyv1index operations by combining multiple Twilio - Proxy endpoints. Agents can delete a specific interaction. and then retrieve a list of all interactions for a session. a maximum of 100 records will in a single workflow.

Example prompt: Call DELETE /v1/Services/{ServiceSid}/Sessions/{SessionSid}/Interactions/{Sid} to delete a specific interaction., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Twilio - Proxy 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 'retrieve a list of interactions for a given [session](https://www.twilio.com/doc', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/Services/{ServiceSid}/Sessions/{SessionSid}/Interactions/{Sid} | Retrieve a list of Interactions for a given [Session](https://www.twilio.com/doc |
| DELETE | /v1/Services/{ServiceSid}/Sessions/{SessionSid}/Interactions/{Sid} | Delete a specific Interaction. |
| GET | /v1/Services/{ServiceSid}/Sessions/{SessionSid}/Interactions | Retrieve a list of all Interactions for a Session. A maximum of 100 records will |
| POST | /v1/Services/{ServiceSid}/Sessions/{SessionSid}/Participants/{ParticipantSid}/MessageInteractions | Create a new message Interaction to send directly from your system to one [Parti |
| GET | /v1/Services/{ServiceSid}/Sessions/{SessionSid}/Participants/{Sid} | Fetch a specific Participant. |
| DELETE | /v1/Services/{ServiceSid}/Sessions/{SessionSid}/Participants/{Sid} | Delete a specific Participant. This is a soft-delete. The participant remains as |
| POST | /v1/Services/{ServiceSid}/Sessions/{SessionSid}/Participants | Add a new Participant to the Session |
| GET | /v1/Services/{ServiceSid}/Sessions/{SessionSid}/Participants | Retrieve a list of all Participants in a Session. |

## Key resources

- **ProxyV1Index** — Operations related to ProxyV1Index
- **ProxyV1Interaction** — Operations related to ProxyV1Interaction
- **ProxyV1MessageInteraction** — Operations related to ProxyV1MessageInteraction
- **ProxyV1Participant** — Operations related to ProxyV1Participant
- **ProxyV1PhoneNumber** — Operations related to ProxyV1PhoneNumber

## Why Jentic

- **Setup:** Wiring Twilio Proxy by hand means setting up HTTP basic auth with your account SID and auth token against the proxy.twilio.com host and handling retries yourself. Through Jentic you install once, import Twilio Proxy from the API Directory, store the account SID and auth token once, and your agent calls it.
- **Permission scoping:** Twilio Proxy puts the service, session, and participant Sids in the URL path (/v1/Services/{ServiceSid}/Sessions/{SessionSid}/Participants/{Sid}), so a rule can pin your agent to one service or session. You choose the operations it may call, so destructive ones like deleting a participant or an interaction 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 interactions for a session' or 'add a participant to a session', and Jentic returns the matching Twilio Proxy 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 - Proxy use?

The Twilio - Proxy 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 retrieve a list of interactions for a given [session](https://www.twilio.com/doc with the Twilio - Proxy?

Yes. Use the GET /v1/Services/{ServiceSid}/Sessions/{SessionSid}/Interactions/{Sid} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

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

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 retrieve a list of interactions for a given [session](https://www.twilio.com/doc through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve a list of interactions for a given [session](https://www.twilio.com/doc'. Jentic returns the matching Twilio - Proxy operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The Twilio - Proxy exposes 30 endpoints covering proxyv1index, proxyv1interaction, proxyv1messageinteraction operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Twilio Proxy operations and credentials the agent may use. The service, session, and participant Sids sit in the URL path, so you can pin the agent to a single service or session, and you choose the exact operations it can call. That means destructive calls like deleting a participant or deleting an interaction stay out of reach unless you explicitly add them.