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

# Termii Messaging API

Termii's Messaging APIs enable you to send messages globally across SMS, Voice, WhatsApp, and Email channels. Each request is assigned a unique ID for tracking delivery status. The API exposes 10 endpoints.

## For AI agents

Programmatically get sender ids, send to number. Covers 10 operations.

## Scope

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

## Capabilities

- Get Sender IDs
- Send to Number
- Verify OTP Token
- Generate In-App Token
- Monitor Termii Messaging API operational status and events

## Use cases

### Communications Operations

Use the Termii Messaging API to perform communications operations programmatically. The API provides 10 endpoints covering core functionality including get sender ids, send to number, send message.

Example prompt: Call GET /sender-id to get sender ids

### Automated Switch Management

Automate switch operations by combining multiple Termii Messaging API endpoints. Agents can send to number and then send message in a single workflow.

Example prompt: Call POST `/sms/number/send` to send to number, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Termii Messaging 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 none tokens manually.

Example prompt: Search Jentic for 'get sender ids', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/sender-id` | Get Sender IDs |
| POST | `/sms/number/send` | Send to Number |
| POST | `/sms/send` | Send Message |
| POST | `/sms/otp/send` | Send OTP Token |
| POST | `/sms/otp/verify` | Verify OTP Token |
| POST | `/sms/otp/generate` | Generate In-App Token |
| GET | `/sms/history/analytics` | Get Message History |
| GET | `/check/dnd` | Search DND Status |

## Key resources

- **Switch** — SMS messaging and sender ID management
- **Token** — OTP token generation and verification
- **Insights** — Analytics, balance, and DND checking

## 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:** 75 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/termii.com/termii/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 Termii Messaging API by hand means handling its API-key auth against the api.ng.termii.com host and coding each SMS, OTP, and sender-id call yourself. Through Jentic you install once, import the Termii Messaging API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Termii carries the destination number and sender in the request body rather than a resource id in the URL path, so limit the agent to the operations it needs, such as sending an SMS or verifying an OTP. You choose the operations it may call, so OTP generation is not included unless you add it.
- **Credential handling:** Your Termii 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' or 'verify a one-time code', and Jentic returns the matching Termii Messaging API 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 Termii Messaging API use?

The Termii Messaging API uses no authentication. 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 sender ids with the Termii Messaging API?

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

### What are the rate limits for the Termii Messaging 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 sender ids through Jentic?

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

### How many endpoints does the Termii Messaging API have?

The Termii Messaging API exposes 10 endpoints covering switch, token, insights operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Termii operations and credentials the agent can use, and you grant only the ones it needs, such as POST `/sms/send` to send an SMS or POST `/sms/otp/verify` to verify a one-time code. Termii carries the destination number and sender in the request body rather than as a resource id in the URL, so scoping happens at the operation level: if you do not enable POST `/sms/otp/generate`, the agent cannot generate OTP tokens. Your stored API key is injected only for the calls you have allowed, so the agent never reaches endpoints you have not approved.