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

# Sendgrid Twilio SendGrid Legacy Marketing Campaigns Campaigns API

The Twilio SendGrid Legacy Marketing Campaigns Campaigns API allows you to manage your marketing email messages programmatically. This API is operational, but we recommend using the current version of Marketing Campaigns to manage your marketing messages with SendGrid [Single Sends](https://docs.sendgrid.com/api-reference/single-sends/) and [Automations](https://docs.sendgrid.com/ui/sending-email/. The API exposes 11 endpoints secured with bearer authentication.

## For AI agents

Programmatically create a campaign, retrieve all campaigns. Covers 11 operations with bearer authentication.

## Scope

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

## Capabilities

- Create a Campaign
- Retrieve all Campaigns
- Update a Campaign
- Delete a Campaign
- Schedule a Campaign
- View Scheduled Time of a Campaign

## Use cases

### Communications Operations

Use the Twilio SendGrid Legacy Marketing Campaigns Campaigns API to perform communications operations programmatically. The API provides 11 endpoints covering core functionality including create a campaign, retrieve all campaigns, retrieve a single campaign.

Example prompt: Call POST `/v3/campaigns` to create a campaign

### Automated Campaigns API Management

Automate campaigns API operations by combining multiple Twilio SendGrid Legacy Marketing Campaigns Campaigns API endpoints. Agents can retrieve all campaigns and then retrieve a single campaign in a single workflow.

Example prompt: Call GET `/v3/campaigns` to retrieve all campaigns, then verify the result

### AI Agent Integration via Jentic

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v3/campaigns` | Create a Campaign |
| GET | `/v3/campaigns` | Retrieve all Campaigns |
| GET | `/v3/campaigns/{campaign_id}` | Retrieve a single campaign |
| PATCH | `/v3/campaigns/{campaign_id}` | Update a Campaign |
| DELETE | `/v3/campaigns/{campaign_id}` | Delete a Campaign |
| POST | `/v3/campaigns/{campaign_id}/schedules` | Schedule a Campaign |
| GET | `/v3/campaigns/{campaign_id}/schedules` | View Scheduled Time of a Campaign |
| PATCH | `/v3/campaigns/{campaign_id}/schedules` | Update a Scheduled Campaign |

## Key resources

- **Campaigns API** — Legacy Marketing Campaigns: Campaigns API

## Why Jentic

- **Setup:** Wiring the Twilio SendGrid Legacy Marketing Campaigns Campaigns API by hand means learning its bearer API key auth, pointing at the api.sendgrid.com host, and handling paging and retries yourself. Through Jentic you install once, import the Campaigns API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** This API puts the campaign id in the URL path (`/v3/campaigns/{campaign_id}`), so a rule can pin your agent to one campaign: it can read and schedule that campaign and nothing else. You choose the operations it may call, so deleting a campaign with DELETE `/v3/campaigns/{campaign_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 campaign' or 'schedule a campaign', and Jentic returns the matching Twilio SendGrid Campaigns API 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 Legacy Marketing Campaigns Campaigns API use?

The Twilio SendGrid Legacy Marketing Campaigns Campaigns 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 campaign with the Twilio SendGrid Legacy Marketing Campaigns Campaigns API?

Yes. Use the POST `/v3/campaigns` 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 Campaigns 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 campaign through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a campaign'. Jentic returns the matching Twilio SendGrid Legacy Marketing Campaigns Campaigns 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 Campaigns API have?

The Twilio SendGrid Legacy Marketing Campaigns Campaigns API exposes 11 endpoints covering campaigns API operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which SendGrid operations the agent may call and which credentials it may use. Since this API puts the campaign id in the URL path (`/v3/campaigns/{campaign_id}`), you can pin the agent to a single campaign so it only reads and schedules that campaign and nothing else. You choose the allowed operations, so a destructive call like DELETE `/v3/campaigns/{campaign_id}` is excluded unless you explicitly add it.