canonical: https://jentic.com/apis/sendgrid.com/twilio-sendgrid-verified-senders-api

# Sendgrid Twilio SendGrid Verified Senders API

The Twilio SendGrid Verified Senders API allows you to programmatically manage the Sender Identities that are authorized to send email for your account. You can also manage Sender Identities in the [SendGrid application user interface](https://app.sendgrid.com/settings/sender_auth). See [**Single Sender Verification**](https://sendgrid.com/docs/ui/sending-email/sender-verification/) for more infor. The API exposes 8 endpoints secured with bearer authentication.

## For AI agents

Programmatically create verified sender request, get all verified senders. Covers 8 operations with bearer authentication.

## Scope

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

## Capabilities

- Create Verified Sender Request
- Get All Verified Senders
- Edit Verified Sender
- Delete Verified Sender
- Domain Warn List
- Resend Verified Sender Request
- Completed Steps

## Use cases

### Communications Operations

Use the Twilio SendGrid Verified Senders API to perform communications operations programmatically. The API provides 8 endpoints covering core functionality including create verified sender request, get all verified senders, edit verified sender.

Example prompt: Call POST /v3/verified_senders to create verified sender request

### Automated Sender Verification Management

Automate sender verification operations by combining multiple Twilio SendGrid Verified Senders API endpoints. Agents can get all verified senders and then edit verified sender in a single workflow.

Example prompt: Call GET /v3/verified_senders to get all verified senders, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Twilio SendGrid Verified Senders API 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 bearer tokens manually.

Example prompt: Search Jentic for 'create verified sender request', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v3/verified_senders | Create Verified Sender Request |
| GET | /v3/verified_senders | Get All Verified Senders |
| PATCH | /v3/verified_senders/{id} | Edit Verified Sender |
| DELETE | /v3/verified_senders/{id} | Delete Verified Sender |
| GET | /v3/verified_senders/domains | Domain Warn List |
| POST | /v3/verified_senders/resend/{id} | Resend Verified Sender Request |
| GET | /v3/verified_senders/steps_completed | Completed Steps |
| GET | /v3/verified_senders/verify/{token} | Verify Sender Request |

## Key resources

- **Sender Verification** — Twilio SendGrid Sender Verification API

## Why Jentic

- **Setup:** Wiring the Twilio SendGrid Verified Senders API by hand means setting up its bearer token auth, choosing the right US or EU host (api.sendgrid.com or api.eu.sendgrid.com), and handling status codes yourself. Through Jentic you install once, import the Verified Senders API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Verified Senders API puts the sender id in the URL path (/v3/verified_senders/{id}), so a rule can pin your agent to one verified sender. You choose the operations it may call, so destructive ones like deleting a sender are not included unless you add them.
- **Credential handling:** Your Twilio SendGrid token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a verified sender request', and Jentic returns the matching Verified Senders operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Pusher** — Alternative communications API

## FAQ

### What authentication does the Twilio SendGrid Verified Senders API use?

The Twilio SendGrid Verified Senders API uses a Bearer token in the Authorization header. 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 verified sender request with the Twilio SendGrid Verified Senders API?

Yes. Use the POST /v3/verified_senders endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Twilio SendGrid Verified Senders API?

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 verified sender request through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create verified sender request'. Jentic returns the matching Twilio SendGrid Verified Senders API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Twilio SendGrid Verified Senders API have?

The Twilio SendGrid Verified Senders API exposes 8 endpoints covering sender verification operations.

### Can I limit what my agent is allowed to do with the SendGrid Verified Senders API?

Yes. Jentic One is self-hosted by you, so your own rules decide which of the eight Verified Senders operations the agent may call and which credentials it may use. Because the sender id sits in the URL path (/v3/verified_senders/{id}), a rule can pin the agent to a single verified sender, and you can allow read-only calls like GET /v3/verified_senders while withholding destructive ones such as DELETE /v3/verified_senders/{id} unless you explicitly add them. Your SendGrid bearer token is stored encrypted by your instance and injected only for the operations you permit.