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

# Sendiio API

Sendiio is an email and SMS marketing platform. The API provides endpoints for managing lists, forms, fields, sequences, webhooks, and authentication. The API exposes 22 endpoints secured with apiKey authentication.

## For AI agents

Programmatically check credentials, subscribe to list (json). Covers 22 operations with apiKey authentication.

## Scope

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

## Capabilities

- Check credentials
- Subscribe to list (JSON)
- Unsubscribe email
- Get email list
- Monitor Sendiio API operational status and events

## Use cases

### Communications Operations

Use the Sendiio API to perform communications operations programmatically. The API provides 22 endpoints covering core functionality including check credentials, subscribe to list (json), subscribe to list (redirect).

Example prompt: Call POST `/auth/check` to check credentials

### Automated Authentication Management

Automate authentication operations by combining multiple Sendiio API endpoints. Agents can subscribe to list (json) and then subscribe to list (redirect) in a single workflow.

Example prompt: Call POST `/lists/subscribe/json` to subscribe to list (json), then verify the result

### AI Agent Integration via Jentic

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth/check` | Check credentials |
| POST | `/lists/subscribe/json` | Subscribe to list (JSON) |
| POST | `/lists/subscribe` | Subscribe to list (redirect) |
| POST | `/lists/{encryptedId}/unsubscribe` | Unsubscribe email |
| POST | `/lists/phone/{encryptedId}/unsubscribe` | Unsubscribe phone |
| GET | `/lists/email/{encryptedId}` | Get email list |
| GET | `/lists/phone/{encryptedId}` | Get phone list |
| GET | `/lists/email` | Get all email lists |

## Key resources

- **Authentication** — Operations related to Authentication
- **Fields** — Operations related to Fields
- **Forms** — Operations related to Forms
- **Lists** — Operations related to Lists
- **Sequences** — Operations related to Sequences

## 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:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/sendiio.com/sendiio/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 the Sendiio API by hand means setting up its dual header auth, sending both the token and secret headers on every request against sendiio.com/api/v1, and handling status codes yourself. Through Jentic you install once, import the Sendiio API from the API Directory, store the token and secret once, and your agent calls it.
- **Permission scoping:** The Sendiio API puts the list id in the URL path (`/lists/email/{encryptedId}` and `/lists/phone/{encryptedId}`), so a rule can pin your agent to one list. You choose the operations it may call, so ones like unsubscribing a contact are not included unless you add them.
- **Credential handling:** Your Sendiio token 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 'subscribe a contact to an email list', and Jentic returns the matching Sendiio 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 Sendiio API use?

The Sendiio API uses an API key passed in the `token` 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 check credentials with the Sendiio API?

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

### What are the rate limits for the Sendiio 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 check credentials through Jentic?

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

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

The Sendiio API exposes 22 endpoints covering authentication, fields, forms operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Sendiio operations the agent may call, so you can allow it to subscribe a contact to a list while withholding operations like unsubscribing an email or phone number. The Sendiio API carries the list id in the URL path, as in `/lists/email/{encryptedId}` and `/lists/phone/{encryptedId}`, so a rule can pin the agent to one specific list. Your token and secret are held by your own Jentic One instance and injected only for the calls you have permitted.