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

# Sendspark API

API for creating and managing dynamic video campaigns and prospects in Sendspark. The API exposes 7 endpoints secured with apiKey authentication.

## For AI agents

Programmatically API health status, create dynamic video campaign. Covers 7 operations with apiKey authentication.

## Scope

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

## Capabilities

- API health status
- Create dynamic video campaign
- List dynamic video campaigns
- Get dynamic campaign by ID
- Add single prospect to campaign

## Use cases

### Marketing Operations

Use the Sendspark API to perform marketing operations programmatically. The API provides 7 endpoints covering core functionality including API health status, create dynamic video campaign, list dynamic video campaigns.

Example prompt: Call GET `/v1/auth/health` to API health status

### Automated Dynamic Campaigns Management

Automate dynamic campaigns operations by combining multiple Sendspark API endpoints. Agents can create dynamic video campaign and then list dynamic video campaigns in a single workflow.

Example prompt: Call POST `/v1/workspaces/{workspaceId}/dynamics` to create dynamic video campaign, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Sendspark 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 'API health status', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/auth/health` | API health status |
| POST | `/v1/workspaces/{workspaceId}/dynamics` | Create dynamic video campaign |
| GET | `/v1/workspaces/{workspaceId}/dynamics` | List dynamic video campaigns |
| GET | `/v1/workspaces/{workspaceId}/dynamics/{dynamicId}` | Get dynamic campaign by ID |
| GET | `/v1/workspaces/{workspaceId}/dynamics/{dynamicId}/prospects/{email}` | Get prospect by email |
| POST | `/v1/workspaces/{workspaceId}/dynamics/{dynamicId}/prospect` | Add single prospect to campaign |
| POST | `/v1/workspaces/{workspaceId}/dynamics/{dynamicsId}/prospects/bulk` | Add multiple prospects in bulk |

## Key resources

- **Dynamic Campaigns** — Operations related to Dynamic Campaigns
- **Health** — Operations related to Health
- **Prospects** — Operations related to Prospects

## Why Jentic

- **Setup:** Wiring Sendspark by hand means sending both the x-api-key and x-api-secret headers on every request and carrying the workspace id through each call yourself. Through Jentic you install once, import Sendspark from the API Directory, store the key and secret once, and your agent calls it.
- **Permission scoping:** Sendspark puts the workspace and dynamic ids in the URL path (`/v1/workspaces/{workspaceId}/dynamics/{dynamicId}/...`), so a rule can pin your agent to one workspace: it can add prospects to that workspace's dynamics and nothing else. You choose the operations it may call, so bulk prospect creation is not included unless you add it.
- **Credential handling:** Your Sendspark key and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list dynamics in a workspace' or 'add a prospect', and Jentic returns the matching Sendspark 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 Sendspark API use?

The Sendspark 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 API health status with the Sendspark API?

Yes. Use the GET `/v1/auth/health` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Sendspark 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 API health status through Jentic?

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

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

The Sendspark API exposes 7 endpoints covering dynamic campaigns, health, prospects operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Sendspark operations and credentials the agent may use. Since Sendspark carries the workspace and dynamic ids in the URL path, such as `/v1/workspaces/{workspaceId}/dynamics/{dynamicId}`, you can pin the agent to a single workspace so it only adds prospects to that workspace's dynamic campaigns. You also choose the specific operations it may call, so it can list dynamics and add a single prospect while bulk prospect creation stays off unless you grant it.