canonical: https://jentic.com/apis/routee.net/routee

# Routee API

Routee is a cloud communications platform providing SMS, voice, WhatsApp, Viber, email, and two-factor authentication APIs. It enables businesses to send messages, make calls, manage contacts, and handle number verification. The API exposes 28 endpoints secured with bearer authentication.

## For AI agents

Programmatically send a single sms, send bulk sms campaign. Covers 28 operations with bearer authentication.

## Scope

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

## Capabilities

- Send a single SMS
- Analyze SMS content
- Track a single SMS
- Retrieve campaign details
- Update a scheduled SMS campaign

## Use cases

### Communications Operations

Use the Routee API to perform communications operations programmatically. The API provides 28 endpoints covering core functionality including send a single sms, send bulk sms campaign, analyze sms content.

Example prompt: Call POST /sms to send a single sms

### Automated Account Management

Automate account operations by combining multiple Routee API endpoints. Agents can send bulk sms campaign and then analyze sms content in a single workflow.

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

### AI Agent Integration via Jentic

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/sms` | Send a single SMS |
| POST | `/sms/campaign` | Send bulk SMS campaign |
| POST | `/sms/analyze` | Analyze SMS content |
| GET | `/sms/tracking/single/{trackingId}` | Track a single SMS |
| GET | `/sms/campaign/{campaignId}/tracking` | Track SMS campaign messages |
| GET | `/sms/campaign/{campaignId}` | Retrieve campaign details |
| PUT | `/sms/campaign/{campaignId}` | Update a scheduled SMS campaign |
| DELETE | `/sms/campaign/{campaignId}` | Delete a scheduled SMS campaign |

## Key resources

- **Account** — Operations related to Account
- **Contacts** — Operations related to Contacts
- **Email** — Operations related to Email
- **Numbers** — Operations related to Numbers
- **SMS** — Operations related to SMS

## Why Jentic

- **Setup:** Wiring the Routee API by hand means holding its bearer token and sending it on every messaging request and handling the request plumbing yourself. Through Jentic you install once, import the Routee API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Routee puts the campaign id in the URL path (`/sms/campaign/{campaignId}`), so a rule can pin your agent to reading and tracking a given campaign. You choose the operations it may call, so ones like sending SMS or deleting a campaign are not included unless you add them.
- **Credential handling:** Your Routee 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 single SMS' or 'track an SMS campaign', and Jentic returns the matching Routee 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 Routee API use?

The Routee 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 single sms with the Routee API?

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

### What are the rate limits for the Routee 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 single sms through Jentic?

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

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

The Routee API exposes 28 endpoints covering account, contacts, email operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Routee operations and credentials your agent may use. Because Routee puts the campaign id in the URL path (`/sms/campaign/{campaignId}`), you can pin an agent to reading and tracking a given campaign while leaving write operations out. Operations like sending an SMS (POST /sms) or deleting a scheduled campaign (DELETE `/sms/campaign/{campaignId}`) are only available if you explicitly add them.