Twilio - Preview

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

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlbasic34 EndpointsREST

Install Jentic One Beta

Connect the Twilio - Preview to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twilio - Preview, 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 - Preview API.

Updates a specific AuthorizationDocument.

Fetch a specific AuthorizationDocument.

Create an AuthorizationDocument for authorizing the hosting of phone number capa

Retrieve a list of AuthorizationDocuments belonging to the account initiating th

GET STARTED

Start building with Twilio - Preview API

Explore with Jentic

View OpenAPI Document

For Agents

Programmatically updates a specific authorizationdocument., fetch a specific authorizationdocument.. Covers 34 operations with basic authentication.

Use for: I need to updates a specific authorizationdocument., I want to fetch a specific authorizationdocument., Search for an authorizationdocument for authorizing the hosting of phone number capa, Find all a list of authorizationdocuments belonging to the account initiating th

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

Use Cases

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

★ Developer Tools Operations

Use the Twilio - Preview to perform developer tools operations programmatically. The API provides 34 endpoints covering core functionality including updates a specific authorizationdocument., fetch a specific authorizationdocument., create an authorizationdocument for authorizing the hosting of phone number capa.

Call POST /HostedNumbers/AuthorizationDocuments/{Sid} to updates a specific authorizationdocument.

Automated PreviewHostedNumbersAuthorizationDocument Management

Automate previewhostednumbersauthorizationdocument operations by combining multiple Twilio - Preview endpoints. Agents can fetch a specific authorizationdocument. and then create an authorizationdocument for authorizing the hosting of phone number capa in a single workflow.

Call GET /HostedNumbers/AuthorizationDocuments/{Sid} to fetch a specific authorizationdocument., then verify the result

AI Agent Integration via Jentic

AI agents discover and call Twilio - Preview 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 'updates a specific authorizationdocument.', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

34 endpoints — this is the public twilio rest api.

METHOD

PATH

DESCRIPTION

POST

/HostedNumbers/AuthorizationDocuments/{Sid}

Updates a specific AuthorizationDocument.

GET

/HostedNumbers/AuthorizationDocuments/{Sid}

Fetch a specific AuthorizationDocument.

POST

/HostedNumbers/AuthorizationDocuments

Create an AuthorizationDocument for authorizing the hosting of phone number capa

GET

/HostedNumbers/AuthorizationDocuments

Retrieve a list of AuthorizationDocuments belonging to the account initiating th

GET

/HostedNumbers/AuthorizationDocuments/{SigningDocumentSid}/DependentHostedNumberOrders

Retrieve a list of dependent HostedNumberOrders belonging to the AuthorizationDo

POST

/HostedNumbers/HostedNumberOrders/{Sid}

Updates a specific HostedNumberOrder.

GET

/HostedNumbers/HostedNumberOrders/{Sid}

Fetch a specific HostedNumberOrder.

DELETE

/HostedNumbers/HostedNumberOrders/{Sid}

Cancel the HostedNumberOrder (only available when the status is in `received`).

POST

/HostedNumbers/AuthorizationDocuments/{Sid}

Updates a specific AuthorizationDocument.

GET

/HostedNumbers/AuthorizationDocuments/{Sid}

Fetch a specific AuthorizationDocument.

POST

/HostedNumbers/AuthorizationDocuments

Create an AuthorizationDocument for authorizing the hosting of phone number capa

GET

/HostedNumbers/AuthorizationDocuments

Retrieve a list of AuthorizationDocuments belonging to the account initiating th

GET

/HostedNumbers/AuthorizationDocuments/{SigningDocumentSid}/DependentHostedNumberOrders

Retrieve a list of dependent HostedNumberOrders belonging to the AuthorizationDo

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 'update an authorization document' or 'list hosted number orders', and Jentic returns the matching Twilio Preview 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 - Preview API through Jentic.

What authentication does the Twilio - Preview use?

The Twilio - Preview 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 updates a specific authorizationdocument. with the Twilio - Preview?

Yes. Use the POST /HostedNumbers/AuthorizationDocuments/{Sid} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Twilio - Preview?

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 updates a specific authorizationdocument. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'updates a specific authorizationdocument.'. Jentic returns the matching Twilio - Preview operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Twilio - Preview have?

The Twilio - Preview exposes 34 endpoints covering previewhostednumbersauthorizationdocument, previewhostednumbersdependenthostednumberorder, previewhostednumbershostednumberorder operations.

Can I limit what my agent is allowed to do with the Twilio Preview API?

Yes. Because you run Jentic One yourself, your own rules decide which Twilio Preview operations and credentials the agent may use. Twilio Preview puts the resource Sid in the URL path, such as /HostedNumbers/AuthorizationDocuments/{Sid}, so you can pin the agent to a single authorization document or hosted number order. You also choose which operations it may call, so a destructive request like canceling a hosted number order stays out of reach unless you add it.