Twilio - Proxy

Name: Twilio - Proxy API
Brand: Twilio - Proxy
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlbasic30 EndpointsREST

Install Jentic One Beta

Connect the Twilio - Proxy to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twilio - Proxy, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Twilio - Proxy API.

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

GET STARTED

Start building with Twilio - Proxy API

Explore with Jentic

View OpenAPI Document

For 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.

Use for: I need to a list of interactions for a given [session](https://www.twilio.com/doc, I want to a specific interaction., Search for a list of all interactions for a session. a maximum of 100 records will, Find all a new message interaction to send directly from your system to one [parti

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

Use Cases

Patterns agents use Twilio - Proxy API for, with concrete tasks.

★ 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.

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.

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.

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

30 endpoints — this is the public twilio rest api.

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.

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.

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Twilio - Proxy API through Jentic.

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.