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

# SendPulse API

SendPulse REST API for email marketing, mailing lists, campaigns, and account management. The API exposes 23 endpoints secured with bearer authentication.

## For AI agents

Programmatically obtain an oauth 2.0 access token, get account information. Covers 23 operations with bearer authentication.

## Scope

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

## Capabilities

- Obtain an OAuth 2.0 access token
- Get account information
- Create a mailing list
- Query and filter SendPulse API records by parameters
- Monitor SendPulse API operational status and events

## Use cases

### Marketing Operations

Use the SendPulse API to perform marketing operations programmatically. The API provides 23 endpoints covering core functionality including obtain an oauth 2.0 access token, get account information, get team members details.

Example prompt: Call POST `/oauth/access_token` to obtain an oauth 2.0 access token

### Automated Authentication Management

Automate authentication operations by combining multiple SendPulse API endpoints. Agents can get account information and then get team members details in a single workflow.

Example prompt: Call GET `/user/info` to get account information, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SendPulse 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 'obtain an oauth 2.0 access token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/oauth/access_token` | Obtain an OAuth 2.0 access token |
| GET | `/user/info` | Get account information |
| GET | `/user/invited-users-list` | Get team members details |
| GET | `/user/balance/detail` | Get detailed balance information |
| POST | `/addressbooks` | Create a mailing list |
| GET | `/addressbooks` | Get all mailing lists |
| GET | `/addressbooks/{id}` | Get mailing list info |
| PUT | `/addressbooks/{id}` | Edit a mailing list |

## Key resources

- **Authentication** — OAuth 2.0 authentication
- **Account** — Account and user information
- **MailingLists** — Mailing list (address book) management
- **Campaigns** — Email campaign management

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 64 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 60 / 100
- **View full report:** https://jentic.com/apis/sendpulse.com/sendpulse/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring SendPulse by hand means exchanging your client credentials at `/oauth/access_token` for a bearer token, refreshing it as it expires, and threading it onto every marketing call yourself. Through Jentic you install once, import SendPulse from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** SendPulse puts the address book id in the URL path (`/addressbooks/{id}/...`), so a rule can pin your agent to one address book: it can read and update contacts there and nothing else. You choose the operations it may call, so a book-level delete is not included unless you add it.
- **Credential handling:** Your SendPulse token 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 an address book' or 'get account balance', and Jentic returns the matching SendPulse 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 SendPulse API use?

The SendPulse 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 obtain an oauth 2.0 access token with the SendPulse API?

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

### What are the rate limits for the SendPulse 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 obtain an oauth 2.0 access token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'obtain an oauth 2.0 access token'. Jentic returns the matching SendPulse API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The SendPulse API exposes 23 endpoints covering authentication, account, mailinglists operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which SendPulse operations and credentials the agent may use. Since SendPulse puts the address book id in the URL path (`/addressbooks/{id}/...`), you can pin the agent to a single address book so it reads and updates contacts there and touches nothing else. You choose the operations it can call, so a book-level delete stays out of reach unless you explicitly add it.