canonical: https://jentic.com/apis/sparkpost.com/sparkpost

# SparkPost API

SparkPost is a cloud-based email delivery service that provides comprehensive APIs for sending, tracking, and analyzing email campaigns and transactional messages. The API exposes 27 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a transmission, list scheduled transmissions. Covers 27 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create a transmission
- List scheduled transmissions
- Get transmission details
- Delete scheduled transmission
- Monitor SparkPost API operational status and events

## Use cases

### Communications Operations

Use the SparkPost API to perform communications operations programmatically. The API provides 27 endpoints covering core functionality including create a transmission, list scheduled transmissions, get transmission details.

Example prompt: Call POST /transmissions to create a transmission

### Automated Transmissions Management

Automate transmissions operations by combining multiple SparkPost API endpoints. Agents can list scheduled transmissions and then get transmission details in a single workflow.

Example prompt: Call GET /transmissions to list scheduled transmissions, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SparkPost 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 apiKey tokens manually.

Example prompt: Search Jentic for 'create a transmission', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /transmissions | Create a transmission |
| GET | /transmissions | List scheduled transmissions |
| GET | /transmissions/{id} | Get transmission details |
| DELETE | /transmissions/{id} | Delete scheduled transmission |
| GET | /metrics/deliverability | Get deliverability metrics |
| GET | /metrics/deliverability/time-series | Get time-series metrics |
| GET | /metrics/deliverability/domain | Get metrics by domain |
| POST | /templates | Create a template |

## Key resources

- **Transmissions** — Send email messages
- **Metrics** — Analytics and reporting
- **Templates** — Email templates
- **Recipients** — Recipient management
- **Webhooks** — Event webhooks

## Why Jentic

- **Setup:** Wiring SparkPost by hand means sending your key in the X-API-Key header, choosing the US or EU host, and wiring transmissions, templates, and deliverability metrics yourself. Through Jentic you install once, import the SparkPost API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The recipients of a SparkPost transmission travel in the request body, not a resource path, so limit the agent to the operations it needs, such as creating a transmission or reading deliverability metrics. You choose the operations it may call, so a destructive one like deleting a transmission is not included unless you add it.
- **Credential handling:** Your SparkPost 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 'send an email' or 'get deliverability metrics over time', and Jentic returns the matching SparkPost operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

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

## FAQ

### What authentication does the SparkPost API use?

The SparkPost API uses an API key passed in the `X-API-Key` 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 transmission with the SparkPost API?

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

### What are the rate limits for the SparkPost 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 transmission through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a transmission'. Jentic returns the matching SparkPost API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the SparkPost API have?

The SparkPost API exposes 27 endpoints covering transmissions, metrics, templates operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which SparkPost operations and credentials the agent may use, so you can grant only what it needs, such as creating a transmission or reading deliverability metrics. A destructive operation like deleting a scheduled transmission stays out of reach unless you explicitly add it. Note that transmission recipients travel in the request body rather than a resource path, so scoping is done at the operation level rather than per recipient.