Routee API

Name: Routee API API
Brand: Routee API
Availability: InStock

✓ Official Vendor SpecCommunicationsVoice Telephonybearer28 EndpointsREST

For Agents

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

Use for: I need to send a single sms, I want to send bulk sms campaign, Search for analyze sms content, Find all track a single sms

Connect the Routee API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Routee API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Routee API API.

Send a single SMS

Analyze SMS content

Track a single SMS

Retrieve campaign details

Update a scheduled SMS campaign

GET STARTED

Start building with Routee API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Routee API API for, with concrete tasks.

★ 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.

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.

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.

Search Jentic for 'send a single sms', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

28 endpoints — routee is a cloud communications platform providing sms, voice, whatsapp, viber, email, and two-factor authentication apis.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Routee API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'send a single sms') and Jentic returns the matching Routee API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Routee API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio

Alternative communications API

Choose Twilio when you need a different approach to communications operations

Alternative

Sendgrid

Alternative communications API

Choose Sendgrid when you need a different approach to communications operations

Complementary

Pusher

Complementary communications API

Choose Pusher when you need a complementary approach to communications operations

FAQs

Specific to using Routee API API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.