Termii Messaging API

Name: Termii Messaging API
Brand: Termii Messaging API
Availability: InStock

✓ Official Vendor SpecCommunicationsEmail Deliverynone10 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Termii Messaging API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Termii Messaging 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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftermii.com%2Ftermii" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftermii.com%2Ftermii" | 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 Termii Messaging API.

Get Sender IDs

Send to Number

Verify OTP Token

Generate In-App Token

GET STARTED

Start building with Termii Messaging API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Termii Messaging API for, with concrete tasks.

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

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.

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.

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

Key Endpoints

10 endpoints — termii's messaging apis enable you to send messages globally across sms, voice, whatsapp, and email channels.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Termii Messaging API through Jentic.

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.

Termii Messaging API

Connect the Termii Messaging API to your agent

Capabilities

Start building with Termii Messaging API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs