Twilio - Events
Browse all Twilio APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlbasic22 EndpointsREST
For Agents
Programmatically retrieve a paginated list of all the available event types., fetch a specific event type.. Covers 22 operations with basic authentication.
Use for: I need to a paginated list of all the available event types., I want to fetch a specific event type., Search for fetch a specific schema with its nested versions., Find all a paginated list of versions of the schema.
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
This is the public Twilio REST API. The API exposes 22 endpoints secured with basic authentication.
Install Jentic One Beta
Connect the Twilio - Events to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twilio - Events, 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftwilio.com%2Ftwilio---events" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftwilio.com%2Ftwilio---events" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 - Events API.
Retrieve a paginated list of all the available Event Types.
Fetch a specific Event Type.
Update a specific Sink
Query and filter Twilio - Events records by parameters
Monitor Twilio - Events operational status and events
Use Cases
Patterns agents use Twilio - Events API for, with concrete tasks.
★ Developer Tools Operations
Use the Twilio - Events to perform developer tools operations programmatically. The API provides 22 endpoints covering core functionality including retrieve a paginated list of all the available event types., fetch a specific event type., fetch a specific schema with its nested versions..
Call GET /v1/Types to retrieve a paginated list of all the available event types.
Automated EventsV1EventType Management
Automate eventsv1eventtype operations by combining multiple Twilio - Events endpoints. Agents can fetch a specific event type. and then fetch a specific schema with its nested versions. in a single workflow.
Call GET /v1/Types/{Type} to fetch a specific event type., then verify the result
AI Agent Integration via Jentic
AI agents discover and call Twilio - Events 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 paginated list of all the available event types.', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
22 endpoints — this is the public twilio rest api.
METHOD
PATH
DESCRIPTION
GET
/v1/Types
Retrieve a paginated list of all the available Event Types.
GET
/v1/Types/{Type}
Fetch a specific Event Type.
GET
/v1/Schemas/{Id}
Fetch a specific schema with its nested versions.
GET
/v1/Schemas/{Id}/Versions
Retrieve a paginated list of versions of the schema.
GET
/v1/Schemas/{Id}/Versions/{SchemaVersion}
Fetch a specific schema and version.
POST
/v1/Sinks/{Sid}
Update a specific Sink
GET
/v1/Sinks/{Sid}
Fetch a specific Sink.
DELETE
/v1/Sinks/{Sid}
Delete a specific Sink.
GET
/v1/Types
Retrieve a paginated list of all the available Event Types.
GET
/v1/Types/{Type}
Fetch a specific Event Type.
GET
/v1/Schemas/{Id}
Fetch a specific schema with its nested versions.
GET
/v1/Schemas/{Id}/Versions
Retrieve a paginated list of versions of the schema.
GET
/v1/Schemas/{Id}/Versions/{SchemaVersion}
Fetch a specific schema and version.
POST
/v1/Sinks/{Sid}
Update a specific Sink
GET
/v1/Sinks/{Sid}
Fetch a specific Sink.
DELETE
/v1/Sinks/{Sid}
Delete a specific Sink.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Twilio Events by hand means setting up HTTP basic auth with your Account SID and Auth Token, pointing at the events.twilio.com host, and handling pagination and retries across event types, schemas, and sinks yourself. Through Jentic you install once, import Twilio Events from the API Directory, store the Account SID and Auth Token once, and your agent calls it.
Permission scoping
Twilio Events puts the sink and schema ids in the URL path (/v1/Sinks/{Sid}, /v1/Schemas/{Id}), so a rule can pin your agent to one sink: it can read or update that sink and nothing else. You choose the operations it may call, so destructive ones like deleting a sink are not included unless you add them.
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 'retrieve a paginated list of all available event types', and Jentic returns the matching Twilio Events operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
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
FAQs
Specific to using Twilio - Events API through Jentic.
What authentication does the Twilio - Events use?
The Twilio - Events 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 paginated list of all the available event types. with the Twilio - Events?
Yes. Use the GET /v1/Types endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Twilio - Events?
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 paginated list of all the available event types. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve a paginated list of all the available event types.'. Jentic returns the matching Twilio - Events operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Twilio - Events have?
The Twilio - Events exposes 22 endpoints covering eventsv1eventtype, eventsv1replay, eventsv1schema operations.
Can I limit what my agent is allowed to do with the Twilio Events API?
Yes. Because you run Jentic One yourself, your own rules decide which Twilio Events operations and credentials the agent may use. Since the API puts the sink and schema ids in the URL path, such as /v1/Sinks/{Sid} and /v1/Schemas/{Id}, you can pin the agent to a single sink so it only reads or updates that one. You also choose which operations are exposed, so destructive calls like deleting a sink are left out unless you add them.
GET STARTED