canonical: https://jentic.com/apis/sendx.io/sendx

# SendX REST API

SendX REST API for managing contacts, campaigns, tags, lists, senders, and webhooks for email marketing and marketing automation. The API exposes 6 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get all contacts, get all campaigns. Covers 6 operations with apiKey authentication.

## Scope

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

## Capabilities

- Get all contacts
- Manage marketing data programmatically
- Integrate SendX REST API into automated workflows
- Query and filter SendX REST API records by parameters
- Monitor SendX REST API operational status and events

## Use cases

### Marketing Operations

Use the SendX REST API to perform marketing operations programmatically. The API provides 6 endpoints covering core functionality including get all contacts, get all campaigns, get all tags.

Example prompt: Call GET /contact to get all contacts

### Automated Campaigns Management

Automate campaigns operations by combining multiple SendX REST API endpoints. Agents can get all campaigns and then get all tags in a single workflow.

Example prompt: Call GET /campaign to get all campaigns, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SendX REST 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 'get all contacts', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/contact` | Get all contacts |
| GET | `/campaign` | Get all campaigns |
| GET | `/tag` | Get all tags |
| GET | `/list` | Get all contact lists |
| GET | `/sender` | Get all verified sender addresses |
| GET | `/webhook` | Get all webhooks |

## Key resources

- **Campaigns** — Operations related to Campaigns
- **Contacts** — Operations related to Contacts
- **Lists** — Operations related to Lists
- **Senders** — Operations related to Senders
- **Tags** — Operations related to Tags

## 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: 100 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 51 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/sendx.io/sendx/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 SendX by hand means setting the X-Team-ApiKey header on every request and handling its contact, campaign, and list calls yourself. Through Jentic you install once, import SendX from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** SendX exposes collection-level endpoints for contacts, campaigns, tags, and lists, so limit the agent to the operations it needs, such as listing contacts or reading campaigns. You choose the operations it may call, so it holds only the read access you grant.
- **Credential handling:** Your SendX 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 'get all contacts' or 'list campaigns', and Jentic returns the matching SendX 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 SendX REST API use?

The SendX REST API uses an API key passed in the `X-Team-ApiKey` 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 get all contacts with the SendX REST API?

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

### What are the rate limits for the SendX REST 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 get all contacts through Jentic?

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

### How many endpoints does the SendX REST API have?

The SendX REST API exposes 6 endpoints covering campaigns, contacts, lists operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which SendX operations and credentials the agent may use. SendX exposes collection-level endpoints for contacts, campaigns, tags, lists, senders, and webhooks, so you can restrict the agent to just the calls it needs, such as GET /contact or GET /campaign, and withhold the rest. Since these are read operations, the agent holds only the read access you explicitly grant.