canonical: https://jentic.com/apis/sendgrid.com/twilio-sendgrid-legacy-marketing-campaigns-sender-

# Sendgrid Twilio SendGrid Legacy Marketing Campaigns Sender Identities API

The Twilio SendGrid Legacy Marketing Campaigns Sender Identites API allows you to manage the email addresses used to send your marketing email. This API is operational, but we recommend using the current version of Marketing Campaigns to manage your [senders](https://docs.sendgrid.com/api-reference/senders/). See [**Migrating from Legacy Marketing Campaigns**](https://docs.sendgrid.com/ui/sending-. The API exposes 6 endpoints secured with bearer authentication.

## For AI agents

Programmatically create a sender identity, get all sender identities. Covers 6 operations with bearer authentication.

## Scope

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

## Capabilities

- Create a Sender Identity
- Get all Sender Identities
- View a Sender Identity
- Update a Sender Identity
- Delete a Sender Identity
- Resend Sender Identity Verification

## Use cases

### Marketing Operations

Use the Twilio SendGrid Legacy Marketing Campaigns Sender Identities API to perform marketing operations programmatically. The API provides 6 endpoints covering core functionality including create a sender identity, get all sender identities, view a sender identity.

Example prompt: Call POST /v3/senders to create a sender identity

### Automated Sender Identities Management

Automate sender identities operations by combining multiple Twilio SendGrid Legacy Marketing Campaigns Sender Identities API endpoints. Agents can get all sender identities and then view a sender identity in a single workflow.

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

### AI Agent Integration via Jentic

AI agents discover and call Twilio SendGrid Legacy Marketing Campaigns Sender Identities 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 a sender identity', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v3/senders | Create a Sender Identity |
| GET | /v3/senders | Get all Sender Identities |
| GET | /v3/senders/{sender_id} | View a Sender Identity |
| PATCH | /v3/senders/{sender_id} | Update a Sender Identity |
| DELETE | /v3/senders/{sender_id} | Delete a Sender Identity |
| POST | /v3/senders/{sender_id}/resend_verification | Resend Sender Identity Verification |

## Key resources

- **Sender Identities** — Twilio SendGrid Legacy Marketing Campaigns Sender Identities API

## Why Jentic

- **Setup:** Wiring the Twilio SendGrid Legacy Marketing Campaigns Sender Identities API by hand means learning its bearer API key auth, pointing at the api.sendgrid.com host, and handling retries yourself. Through Jentic you install once, import the Sender Identities API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** This API puts the sender id in the URL path (/v3/senders/{sender_id}), so a rule can pin your agent to one sender identity: it can read and resend verification for that sender and nothing else. You choose the operations it may call, so deleting a sender with DELETE /v3/senders/{sender_id} is not included unless you add it.
- **Credential handling:** Your Twilio SendGrid API key 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 sender identity' or 'resend sender verification', and Jentic returns the matching Twilio SendGrid Sender Identities API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mailchimp** — Alternative marketing API
- **Hubspot** — Alternative marketing API

## FAQ

### What authentication does the Twilio SendGrid Legacy Marketing Campaigns Sender Identities API use?

The Twilio SendGrid Legacy Marketing Campaigns Sender Identities 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 a sender identity with the Twilio SendGrid Legacy Marketing Campaigns Sender Identities API?

Yes. Use the POST /v3/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 Legacy Marketing Campaigns Sender Identities 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 a sender identity through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a sender identity'. Jentic returns the matching Twilio SendGrid Legacy Marketing Campaigns Sender Identities API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Twilio SendGrid Legacy Marketing Campaigns Sender Identities API have?

The Twilio SendGrid Legacy Marketing Campaigns Sender Identities API exposes 6 endpoints covering sender identities operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which of the six sender-identity operations the agent may call and which stored SendGrid API key it uses. Since this API carries the sender id in the URL path (/v3/senders/{sender_id}), you can pin the agent to a single sender identity, letting it view that sender and resend its verification while nothing else is reachable. Destructive calls such as DELETE /v3/senders/{sender_id} stay excluded until you explicitly grant them.