canonical: https://jentic.com/apis/twilio.com/twilio---routes # Twilio - Routes This is the public Twilio REST API. The API exposes 6 endpoints secured with basic authentication. ## For AI 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. ## Scope Does not handle payments, communications, or crm - use for maps and geolocation only. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'assign an inbound processing region to a phone number.', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | 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. | ## Key resources - **RoutesV2PhoneNumber** — Operations related to RoutesV2PhoneNumber - **RoutesV2SipDomain** — Operations related to RoutesV2SipDomain - **RoutesV2Trunk** — Operations related to RoutesV2Trunk ## Why Jentic - **Setup:** Wiring Twilio Routes by hand means setting up HTTP basic auth with your account SID and auth token against the routes.twilio.com host and handling retries yourself. Through Jentic you install once, import Twilio Routes from the API Directory, store the account SID and auth token once, and your agent calls it. - **Permission scoping:** Twilio Routes puts the phone number or SIP trunk domain in the URL path (/v2/PhoneNumbers/{PhoneNumber}), so a rule can pin your agent to one phone number or trunk. You choose the operations it may call, so updating an inbound processing region is not included unless you add it. - **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 'assign an inbound processing region to a phone number' or 'read a trunk route', and Jentic returns the matching Twilio Routes operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Here** — Alternative maps geolocation API - **Tomtom** — Alternative maps geolocation API - **Googleapis** — Complementary maps geolocation API ## FAQ ### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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. ### Can I limit what my agent is allowed to do with the Twilio Routes API? Yes. Because you run Jentic One yourself, your own rules decide which Twilio Routes operations and credentials the agent may use. Since the phone number or SIP trunk domain sits in the URL path, such as /v2/PhoneNumbers/{PhoneNumber}, you can pin the agent to a single phone number or trunk. You also choose which operations it can call, so assigning an inbound processing region stays off limits unless you explicitly allow it, while read-only fetches can be permitted on their own.