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

# SendZen API

SendZen is a messaging platform for sending WhatsApp messages, including plain text, rich media, templates, utility notifications, and authentication OTPs. The API exposes 1 endpoints secured with bearer authentication.

## For AI agents

Programmatically send a message. Covers 1 operations with bearer authentication.

## Scope

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

## Capabilities

- Send a message
- Manage communications data programmatically
- Integrate SendZen API into automated workflows
- Query and filter SendZen API records by parameters
- Monitor SendZen API operational status and events

## Use cases

### Communications Operations

Use the SendZen API to perform communications operations programmatically. The API provides 1 endpoints covering core functionality including send a message.

Example prompt: Call POST `/v1/messages` to send a message

### Data Retrieval and Monitoring

Query SendZen API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary SendZen API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/messages` | Send a message |

## Key resources

- **Messages** — Operations related to Messages

## 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: 94 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 43 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/sendzen.io/sendzen/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 SendZen by hand means obtaining a bearer token and attaching it to every message request yourself. Through Jentic you install once, import SendZen from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** SendZen sends the message target in the request body, not the URL path, so limit the agent to the operations it needs, such as sending a message. You choose the operations it may call, so it holds only that capability unless you add more.
- **Credential handling:** Your SendZen 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 'send a message', and Jentic returns the matching SendZen 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 SendZen API use?

The SendZen 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 send a message with the SendZen API?

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

### What are the rate limits for the SendZen 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 send a message through Jentic?

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

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

The SendZen API exposes 1 endpoints covering messages operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which SendZen operations and credentials the agent may use. Since the SendZen API exposes only the send-a-message operation (POST `/v1/messages`) and carries the message target in the request body rather than the URL path, you scope the agent to just that operation, and it holds only that capability unless you grant more. Your bearer token is stored once by your own Jentic One instance and injected at execution time, so the agent can send messages without ever seeing the raw secret.