canonical: https://jentic.com/apis/sendgrid.com/twilio-sendgrid-marketing-campaigns-single-sends-a

# Sendgrid Twilio SendGrid Marketing Campaigns Single Sends API

The Twilio SendGrid Single Sends API allows you to create, manage, and send Single Sends. You can also search Single Sends and retrieve statistics about them to help you maintain, alter, and further develop your campaigns. A Single Send is a one-time non-automated email message delivered to a list or segment of your audience. A Single Send may be sent immediately or scheduled for future delivery. . The API exposes 11 endpoints secured with bearer authentication.

## For AI agents

Programmatically create single send, get all single sends. Covers 11 operations with bearer authentication.

## Scope

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

## Capabilities

- Create Single Send
- Get All Single Sends
- Bulk Delete Single Sends
- Duplicate Single Send
- Update Single Send
- Delete Single Send by ID

## Use cases

### Marketing Operations

Use the Twilio SendGrid Marketing Campaigns Single Sends API to perform marketing operations programmatically. The API provides 11 endpoints covering core functionality including create single send, get all single sends, bulk delete single sends.

Example prompt: Call POST /v3/marketing/singlesends to create single send

### Automated Single Sends Management

Automate single sends operations by combining multiple Twilio SendGrid Marketing Campaigns Single Sends API endpoints. Agents can get all single sends and then bulk delete single sends in a single workflow.

Example prompt: Call GET /v3/marketing/singlesends to get all single sends, then verify the result

### AI Agent Integration via Jentic

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v3/marketing/singlesends | Create Single Send |
| GET | /v3/marketing/singlesends | Get All Single Sends |
| DELETE | /v3/marketing/singlesends | Bulk Delete Single Sends |
| POST | /v3/marketing/singlesends/{id} | Duplicate Single Send |
| GET | /v3/marketing/singlesends/{id} | Get Single Send by ID |
| PATCH | /v3/marketing/singlesends/{id} | Update Single Send |
| DELETE | /v3/marketing/singlesends/{id} | Delete Single Send by ID |
| PUT | /v3/marketing/singlesends/{id}/schedule | Schedule Single Send |

## Key resources

- **Single Sends** — Twilio SendGrid Marketing Campaigns Single Sends API

## Why Jentic

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

The Twilio SendGrid Marketing Campaigns Single Sends 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 single send with the Twilio SendGrid Marketing Campaigns Single Sends API?

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

### What are the rate limits for the Twilio SendGrid Marketing Campaigns Single Sends 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 single send through Jentic?

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

### How many endpoints does the Twilio SendGrid Marketing Campaigns Single Sends API have?

The Twilio SendGrid Marketing Campaigns Single Sends API exposes 11 endpoints covering single sends operations.

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

Yes. Because you self-host Jentic One, your own rules decide which of the 11 Single Sends operations the agent may call and which credentials it can use. Since the API puts the single send id in the URL path (/v3/marketing/singlesends/{id}), you can pin the agent to one single send so it only reads, duplicates, or schedules that send and nothing else. You pick the operations it may run, so a destructive call like DELETE /v3/marketing/singlesends/{id} stays out of reach unless you explicitly grant it.