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

# Sendr API

Sendr provides personalized page generation, dynamic audio, video generation, and webhook management APIs. The API exposes 13 endpoints secured with apiKey authentication.

## For AI agents

Programmatically verify API key, list page templates. Covers 13 operations with apiKey authentication.

## Scope

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

## Capabilities

- Verify API key
- List page templates
- Get template variables
- Generate personalized Sendr page
- Sendr page webhook handler

## Use cases

### Developer Tools Operations

Use the Sendr API to perform developer tools operations programmatically. The API provides 13 endpoints covering core functionality including verify API key, list page templates, get template variables.

Example prompt: Call GET `/seat/me` to verify API key

### Automated Audio Management

Automate audio operations by combining multiple Sendr API endpoints. Agents can list page templates and then get template variables in a single workflow.

Example prompt: Call GET `/api/v1/page-template/list` to list page templates, then verify the result

### AI Agent Integration via Jentic

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/seat/me` | Verify API key |
| GET | `/api/v1/page-template/list` | List page templates |
| GET | `/api/v1/page-template/{id}/variables` | Get template variables |
| POST | `/api/v1/enrichment/sendr-page` | Generate personalized Sendr page |
| POST | `/api/v1/enrichment/sendr-page-webhook` | Sendr page webhook handler |
| POST | `/api/v1/enrichment/dynamic-audio` | Generate dynamic audio |
| POST | `/api/v1/enrichment/generate-video` | Generate video |
| POST | `/api/v1/webhook` | Create webhook |

## Key resources

- **Audio** — Operations related to Audio
- **Authentication** — Operations related to Authentication
- **Pages** — Operations related to Pages
- **Video** — Operations related to Video
- **Webhooks** — Operations related to Webhooks

## 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: 82 / 100
  - Developer Experience & Jentic Compatibility: 63 / 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/sendr.io/sendr/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 Sendr by hand means setting the X-API-Key header on every request and handling its page-template and enrichment calls yourself. Through Jentic you install once, import Sendr from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Sendr puts the page-template id in the URL path (`/api/v1/page-template/{id}/variables`), so a rule can pin your agent to one template: it can read that template's variables and nothing else. You choose the operations it may call, so webhook creation or secret reveal is not included unless you add it.
- **Credential handling:** Your Sendr 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 'list page templates' or 'generate a personalized video', and Jentic returns the matching Sendr operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Sendr API use?

The Sendr 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 verify API key with the Sendr API?

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

### What are the rate limits for the Sendr 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 verify API key through Jentic?

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

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

The Sendr API exposes 13 endpoints covering audio, authentication, pages operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Sendr operations and credentials the agent may use. Since Sendr puts the template id in the URL path, such as GET `/api/v1/page-template/{id}/variables`, you can pin the agent to a single template so it reads that template's variables and nothing else. You also choose the operations it may call, so actions like creating a webhook via POST `/api/v1/webhook` or generating video stay off limits unless you explicitly grant them.