Twilio - Verify
Browse all Twilio APIs★ Only Publicly Available OpenAPI DocumentData EnrichmentCompany Databasic53 EndpointsREST
For Agents
Programmatically create a new enrollment access token for the entity, fetch an access token for the entity. Covers 53 operations with basic authentication.
Use for: I need to a new enrollment access token for the entity, I want to fetch an access token for the entity, Search for a new bucket for a rate limit, Find all a list of all buckets for a rate limit.
Not supported: Does not handle payments, communications, or crm — use for data enrichment only.
This is the public Twilio REST API. The API exposes 53 endpoints secured with basic authentication.
Install Jentic One Beta
Connect the Twilio - Verify to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twilio - Verify, 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 - Verify API.
Create a new enrollment Access Token for the Entity
Fetch an Access Token for the Entity
Retrieve a list of all Buckets for a Rate Limit.
Update a specific Bucket.
Delete a specific Bucket.
Use Cases
Patterns agents use Twilio - Verify API for, with concrete tasks.
★ Data Enrichment Operations
Use the Twilio - Verify to perform data enrichment operations programmatically. The API provides 53 endpoints covering core functionality including create a new enrollment access token for the entity, fetch an access token for the entity, create a new bucket for a rate limit.
Call POST /v2/Services/{ServiceSid}/AccessTokens to create a new enrollment access token for the entity
Automated VerifyV2AccessToken Management
Automate verifyv2accesstoken operations by combining multiple Twilio - Verify endpoints. Agents can fetch an access token for the entity and then create a new bucket for a rate limit in a single workflow.
Call GET /v2/Services/{ServiceSid}/AccessTokens/{Sid} to fetch an access token for the entity, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Twilio - Verify 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 'create a new enrollment access token for the entity', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
53 endpoints — this is the public twilio rest api.
METHOD
PATH
DESCRIPTION
POST
/v2/Services/{ServiceSid}/AccessTokens
Create a new enrollment Access Token for the Entity
GET
/v2/Services/{ServiceSid}/AccessTokens/{Sid}
Fetch an Access Token for the Entity
POST
/v2/Services/{ServiceSid}/RateLimits/{RateLimitSid}/Buckets
Create a new Bucket for a Rate Limit
GET
/v2/Services/{ServiceSid}/RateLimits/{RateLimitSid}/Buckets
Retrieve a list of all Buckets for a Rate Limit.
POST
/v2/Services/{ServiceSid}/RateLimits/{RateLimitSid}/Buckets/{Sid}
Update a specific Bucket.
GET
/v2/Services/{ServiceSid}/RateLimits/{RateLimitSid}/Buckets/{Sid}
Fetch a specific Bucket.
DELETE
/v2/Services/{ServiceSid}/RateLimits/{RateLimitSid}/Buckets/{Sid}
Delete a specific Bucket.
POST
/v2/Services/{ServiceSid}/Entities/{Identity}/Challenges
Create a new Challenge for the Factor
POST
/v2/Services/{ServiceSid}/AccessTokens
Create a new enrollment Access Token for the Entity
GET
/v2/Services/{ServiceSid}/AccessTokens/{Sid}
Fetch an Access Token for the Entity
POST
/v2/Services/{ServiceSid}/RateLimits/{RateLimitSid}/Buckets
Create a new Bucket for a Rate Limit
GET
/v2/Services/{ServiceSid}/RateLimits/{RateLimitSid}/Buckets
Retrieve a list of all Buckets for a Rate Limit.
POST
/v2/Services/{ServiceSid}/RateLimits/{RateLimitSid}/Buckets/{Sid}
Update a specific Bucket.
GET
/v2/Services/{ServiceSid}/RateLimits/{RateLimitSid}/Buckets/{Sid}
Fetch a specific Bucket.
DELETE
/v2/Services/{ServiceSid}/RateLimits/{RateLimitSid}/Buckets/{Sid}
Delete a specific Bucket.
POST
/v2/Services/{ServiceSid}/Entities/{Identity}/Challenges
Create a new Challenge for the Factor
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Twilio - Verify 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., 'create a new enrollment access token for the entity') and Jentic returns the matching Twilio - Verify operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Twilio - Verify 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 - Verify API through Jentic.
What authentication does the Twilio - Verify use?
The Twilio - Verify 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 create a new enrollment access token for the entity with the Twilio - Verify?
Yes. Use the POST /v2/Services/{ServiceSid}/AccessTokens endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Twilio - Verify?
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 create a new enrollment access token for the entity through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create a new enrollment access token for the entity'. Jentic returns the matching Twilio - Verify operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Twilio - Verify have?
The Twilio - Verify exposes 53 endpoints covering verifyv2accesstoken, verifyv2bucket, verifyv2challenge operations.
GET STARTED