canonical: https://jentic.com/apis/sendit.co.il/sendit-co-il

# Sendit SMS API

Sendit SMS API for sending SMS messages and managing campaigns. Send individual messages or bulk campaigns with scheduling capabilities. The API exposes 2 endpoints secured with apiKey authentication.

## For AI agents

Programmatically send sms or campaign, get message status. Covers 2 operations with apiKey authentication.

## Scope

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

## Capabilities

- Send SMS or campaign
- Get message status
- Integrate Sendit SMS API into automated workflows
- Query and filter Sendit SMS API records by parameters
- Monitor Sendit SMS API operational status and events

## Use cases

### Communications Operations

Use the Sendit SMS API to perform communications operations programmatically. The API provides 2 endpoints covering core functionality including send sms or campaign, get message status.

Example prompt: Call POST `/sms/send` to send sms or campaign

### Data Retrieval and Monitoring

Query Sendit SMS 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 Sendit SMS API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/sms/send` | Send SMS or campaign |
| GET | `/sms/status/{message_id}` | Get message status |

## Key resources

- **SMS** — SMS sending and campaign 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:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 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/sendit.co.il/sendit-co-il/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 Sendit SMS API by hand means setting up its X-API-Key header auth against sendit.co.il/api/v1 and handling status codes yourself. Through Jentic you install once, import the Sendit SMS API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Sendit SMS API sends the message id in the path only to check delivery status, so scope your agent to the operations it needs, such as sending an SMS or reading a message status. You choose the operations it may call, so sending is not included unless you add it.
- **Credential handling:** Your Sendit SMS 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 'send an SMS message', and Jentic returns the matching Sendit SMS 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 Sendit SMS API use?

The Sendit SMS 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 send sms or campaign with the Sendit SMS API?

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

### What are the rate limits for the Sendit SMS 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 sms or campaign through Jentic?

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

### How many endpoints does the Sendit SMS API have?

The Sendit SMS API exposes 2 endpoints covering sms operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Sendit SMS operations and credentials the agent may use. The Sendit SMS API exposes two operations, sending a message with POST `/sms/send` and reading delivery status with GET `/sms/status/{message_id}`, and you grant only the ones the agent needs. If you allow status reads but not sending, the agent can check delivery on a message ID without ever being able to send an SMS.