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

# Sendcrux API

Cold email outreach and automation platform API for managing email campaigns, domain warm-up, and deliverability. The API exposes 5 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create campaign, list campaigns. Covers 5 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create campaign
- List campaigns
- Get campaign
- Query and filter Sendcrux API records by parameters
- Monitor Sendcrux API operational status and events

## Use cases

### Marketing Operations

Use the Sendcrux API to perform marketing operations programmatically. The API provides 5 endpoints covering core functionality including create campaign, list campaigns, get campaign.

Example prompt: Call POST /campaigns to create campaign

### Automated Campaigns Management

Automate campaigns operations by combining multiple Sendcrux API endpoints. Agents can list campaigns and then get campaign in a single workflow.

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

### AI Agent Integration via Jentic

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/campaigns` | Create campaign |
| GET | `/campaigns` | List campaigns |
| GET | `/campaigns/{id}` | Get campaign |
| POST | `/contacts` | Create contact |
| GET | `/contacts` | List contacts |

## Key resources

- **Campaigns** — Email campaign management
- **Contacts** — Contact and list 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:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 59 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/sendcrux.com/sendcrux/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 Sendcrux API by hand means learning its X-API-Key header auth, calling api.sendcrux.com/v1, and managing campaign and contact payloads yourself. Through Jentic you install once, import the Sendcrux API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Sendcrux puts the campaign id in the URL path (`/campaigns/{id}`), so a rule can pin your agent to reading one campaign. You choose the operations it may call, so campaign or contact creation is not included unless you add it.
- **Credential handling:** Your Sendcrux 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 'create a campaign' or 'list contacts', and Jentic returns the matching Sendcrux API 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 Sendcrux API use?

The Sendcrux 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 campaign with the Sendcrux API?

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

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

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

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

The Sendcrux API exposes 5 endpoints covering campaigns, contacts operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Sendcrux operations and credentials the agent may use. You can allow it to only list or get campaigns (GET /campaigns and GET `/campaigns/{id}`) while leaving campaign and contact creation (POST /campaigns, POST /contacts) off the allowed list. Since Sendcrux puts the campaign id in the URL path, a rule can even pin the agent to reading a single campaign.