Twilio - Routes
Browse all Twilio APIs★ Only Publicly Available OpenAPI DocumentMaps GeolocationGeocodingbasic6 EndpointsREST
For Agents
Programmatically assign an inbound processing region to a phone number., fetch the inbound processing region assigned to a phone number.. Covers 6 operations with basic authentication.
Use for: I need to assign an inbound processing region to a phone number., I want to fetch the inbound processing region assigned to a phone number., Search for assign an inbound processing region to a sip trunk, Find all fetch the inbound processing region assigned to a sip trunk.
Not supported: Does not handle payments, communications, or crm — use for maps and geolocation only.
This is the public Twilio REST API. The API exposes 6 endpoints secured with basic authentication.
Install Jentic One Beta
Connect the Twilio - Routes to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twilio - Routes, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 - Routes API.
Assign an Inbound Processing Region to a phone number.
Fetch the Inbound Processing Region assigned to a phone number.
Integrate Twilio - Routes into automated workflows
Query and filter Twilio - Routes records by parameters
Monitor Twilio - Routes operational status and events
Use Cases
Patterns agents use Twilio - Routes API for, with concrete tasks.
★ Maps and Geolocation Operations
Use the Twilio - Routes to perform maps geolocation operations programmatically. The API provides 6 endpoints covering core functionality including assign an inbound processing region to a phone number., fetch the inbound processing region assigned to a phone number., assign an inbound processing region to a sip trunk.
Call POST /v2/PhoneNumbers/{PhoneNumber} to assign an inbound processing region to a phone number.
Automated RoutesV2PhoneNumber Management
Automate routesv2phonenumber operations by combining multiple Twilio - Routes endpoints. Agents can fetch the inbound processing region assigned to a phone number. and then assign an inbound processing region to a sip trunk in a single workflow.
Call GET /v2/PhoneNumbers/{PhoneNumber} to fetch the inbound processing region assigned to a phone number., then verify the result
AI Agent Integration via Jentic
AI agents discover and call Twilio - Routes 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 'assign an inbound processing region to a phone number.', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
6 endpoints — this is the public twilio rest api.
METHOD
PATH
DESCRIPTION
POST
/v2/PhoneNumbers/{PhoneNumber}
Assign an Inbound Processing Region to a phone number.
GET
/v2/PhoneNumbers/{PhoneNumber}
Fetch the Inbound Processing Region assigned to a phone number.
POST
/v2/Trunks/{SipTrunkDomain}
Assign an Inbound Processing Region to a SIP Trunk
GET
/v2/Trunks/{SipTrunkDomain}
Fetch the Inbound Processing Region assigned to a SIP Trunk.
POST
/v2/PhoneNumbers/{PhoneNumber}
Assign an Inbound Processing Region to a phone number.
GET
/v2/PhoneNumbers/{PhoneNumber}
Fetch the Inbound Processing Region assigned to a phone number.
POST
/v2/Trunks/{SipTrunkDomain}
Assign an Inbound Processing Region to a SIP Trunk
GET
/v2/Trunks/{SipTrunkDomain}
Fetch the Inbound Processing Region assigned to a SIP Trunk.
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Twilio - Routes basic credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'assign an inbound processing region to a phone number.') and Jentic returns the matching Twilio - Routes operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Twilio - Routes integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Twilio - Routes API through Jentic.
What authentication does the Twilio - Routes use?
The Twilio - Routes uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I assign an inbound processing region to a phone number. with the Twilio - Routes?
Yes. Use the POST /v2/PhoneNumbers/{PhoneNumber} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Twilio - Routes?
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 assign an inbound processing region to a phone number. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'assign an inbound processing region to a phone number.'. Jentic returns the matching Twilio - Routes operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Twilio - Routes have?
The Twilio - Routes exposes 6 endpoints covering routesv2phonenumber, routesv2sipdomain, routesv2trunk operations.
GET STARTED