Twilio Routes

Twilio Routes is a Twilio API for managing routing information used by Twilio communications traffic.

Type: Tool
Category: Communication
Version: 1.0.0
Provider: InTouch AI
License: MIT

Provided free and as is, without warranty of any kind — including merchantability, fitness for a particular purpose, and the accuracy or completeness of any result. See the licence. You are responsible for checking what this produces before relying on it.

communicationtwilio

Twilio Twilio Routes V2

Twilio Routes is a Twilio API for managing routing information used by Twilio communications traffic.

Base URL: https://routes.twilio.com
Auth: basic (pass your key via the apiKey input)

Operations

fetchphonenumber — GET /v2/PhoneNumbers/{PhoneNumber} — Fetch the Inbound Processing Region assigned to a phone number.
fetchsipdomain — GET /v2/SipDomains/{SipDomain}
fetchtrunks — GET /v2/Trunks/{SipTrunkDomain} — Fetch the Inbound Processing Region assigned to a SIP Trunk.
updatephonenumber — POST /v2/PhoneNumbers/{PhoneNumber} — Assign an Inbound Processing Region to a phone number.
updatesipdomain — POST /v2/SipDomains/{SipDomain}
updatetrunks — POST /v2/Trunks/{SipTrunkDomain} — Assign an Inbound Processing Region to a SIP Trunk

Inputs

apiKey — your twilio-twilio-routes-v2 API key
operation — one of the operations above
path parameters when an operation's path contains {...}
query — optional JSON object of query params
body — JSON object for create/update ops

Example

operation: fetchphonenumber
apiKey: <your key>

Publishes

The keys a later task may reference as {{taskName.key}}. Referencing anything not listed here resolves to nothing at run time.

error
operation
result
status

Input Properties

Every property this tool accepts, from its own tool.iml.

Property	Type	Required	Default	Description
`apiKey`	string	yes	—	DEPRECATED — bind an API Key credential to the task with `credentialName` instead. A key pasted here is stored in the workflow definition in clear and appears in every export of it. Still honoured for workflows built before the change.
`operation`	string	yes	—	One of: fetchphonenumber, fetchsipdomain, fetchtrunks, updatephonenumber, updatesipdomain, updatetrunks
`PhoneNumber`	string	no	—	Path parameter PhoneNumber (required by some operations).
`SipDomain`	string	no	—	Path parameter SipDomain (required by some operations).
`SipTrunkDomain`	string	no	—	Path parameter SipTrunkDomain (required by some operations).
`body`	string	no	—	Request body as a JSON object string (for create/update operations).
`query`	string	no	—	Query-string parameters as a JSON object string, e.g. {"limit": 50}. Parsed and url-encoded onto the request.