canonical: https://jentic.com/apis/twilio.com/twilio---verify

# Twilio - Verify

This is the public Twilio REST API. The API exposes 53 endpoints secured with basic authentication.

## For AI agents

Programmatically create a new enrollment access token for the entity, fetch an access token for the entity. Covers 53 operations with basic authentication.

## Scope

Does not handle payments, communications, or crm - use for data enrichment only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'create a new enrollment access token for the entity', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **VerifyV2AccessToken** — Operations related to VerifyV2AccessToken
- **VerifyV2Bucket** — Operations related to VerifyV2Bucket
- **VerifyV2Challenge** — Operations related to VerifyV2Challenge
- **VerifyV2Entity** — Operations related to VerifyV2Entity
- **VerifyV2Factor** — Operations related to VerifyV2Factor

## Why Jentic

- **Setup:** Wiring Twilio Verify by hand means setting up HTTP basic auth with your account SID and auth token against the verify.twilio.com host and handling retries yourself. Through Jentic you install once, import Twilio Verify from the API Directory, store the account SID and auth token once, and your agent calls it.
- **Permission scoping:** Twilio Verify puts the service, rate limit, and entity ids in the URL path (/v2/Services/{ServiceSid}/RateLimits/{RateLimitSid}/Buckets/{Sid}), so a rule can pin your agent to one service. You choose the operations it may call, so destructive ones like deleting a rate limit bucket are not included unless you add them.
- **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 'create an access token for an entity' or 'start a verification challenge', and Jentic returns the matching Twilio Verify operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Clearbit** — Alternative data enrichment API
- **Fullcontact** — Alternative data enrichment API
- **Hunter** — Complementary data enrichment API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

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

Yes. Because you run Jentic One yourself, your own rules decide which Twilio Verify operations and credentials the agent may use. Since the service, rate limit, and entity ids live in the URL path (like /v2/Services/{ServiceSid}/RateLimits/{RateLimitSid}/Buckets/{Sid}), you can pin the agent to a single service. You also pick the exact operations it can call, so destructive ones such as deleting a rate limit bucket stay out of reach unless you add them.