Mensagia API

Name: Mensagia API
Brand: Mensagia API
Availability: InStock

✓ Official Vendor SpecCommunicationsSms Messagingbearer, apiKey83 EndpointsREST

For Agents

Send SMS, email, and voice messages, manage contact lists, run campaigns, and issue 2FA codes through one multi-channel platform. Bearer or API-token authentication.

Install Jentic One Beta

Connect the Mensagia API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mensagia 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: 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 Mensagia API.

Send single and bulk SMS messages with delivery tracking via the platform's send endpoints

Dispatch transactional and marketing email through the same authenticated client

Build and schedule multi-recipient campaigns across SMS, email, and voice channels

GET STARTED

Start building with Mensagia API

Explore with Jentic

View OpenAPI Document

The Mensagia API is a multi-channel messaging platform covering SMS, email, voice campaigns, two-factor authentication, certified messaging, and contact management across 83 endpoints. Senders can dispatch single or bulk SMS and email, organise contacts into groups, build scheduled campaigns, and receive delivery notifications, all under either bearer-token or API-token authentication. The platform is well suited to teams that want a single integration for transactional notifications, marketing campaigns, and OTP verification without standing up separate vendors per channel.

Use Cases

Patterns agents use Mensagia API for, with concrete tasks.

★ Transactional SMS Notifications

E-commerce and logistics platforms use Mensagia to dispatch order confirmations, shipping updates, and delivery alerts over SMS. The API accepts a single recipient or a batch and returns per-message status, which lets the application reconcile delivery reports against orders and trigger fallbacks when a number is undeliverable.

Call the SMS send endpoint with the customer's phone number and the order-confirmation template, store the returned message ID against the order, then poll for delivery status.

Marketing Campaign Dispatch

Marketing teams build segmented contact groups in Mensagia, then schedule SMS or email campaigns through the platform's campaigns and contacts endpoints. The unified API lets the same workflow target SMS, email, or voice without changing client logic, which simplifies multi-channel reactivation and promotion campaigns.

Create a contact group of customers tagged 'lapsed', schedule an SMS campaign for tomorrow at 10:00 with a promo code, and confirm the scheduled time in the response.

Two-Factor Authentication

Application sign-in flows use Mensagia's 2FA endpoints to send one-time codes by SMS, then verify the code returned by the user. The platform handles code generation, expiry, and verification, which removes the need to build and store OTP state inside the application database.

Trigger a 2FA send to the user's phone, then on the user's submission call the verify endpoint with the code and return success or failure to the sign-in flow.

AI Agent Notification Tooling

An AI assistant orchestrating long-running tasks can notify users by SMS or email through Mensagia. Through Jentic, the agent loads the send-SMS and send-email operations as discoverable tools and dispatches notifications without writing channel-specific HTTP clients, while the platform's balance endpoint lets the agent surface low-credit warnings to the operator.

Search Jentic for 'send an sms', execute the SMS send operation with the user's phone number and message text, then call /balance to log the remaining credit.

Key Endpoints

83 endpoints — the mensagia api is a multi-channel messaging platform covering sms, email, voice campaigns, two-factor authentication, certified messaging, and contact management across 83 endpoints.

METHOD

PATH

DESCRIPTION

POST

/login

Authenticate and obtain a bearer token

GET

/balance

Get current account balance

POST

/balance/requests

Create a balance top-up request

GET

/contacts

List contacts

POST

/contacts

Create a contact

PUT

/contacts/{id}

Update a contact

POST

/login

Authenticate and obtain a bearer token

GET

/balance

Get current account balance

POST

/balance/requests

Create a balance top-up request

GET

/contacts

List contacts

POST

/contacts

Create a contact

PUT

Why Jentic?

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

Credential isolation

Mensagia issues both bearer tokens (via /login) and a query-string `api_token`. Jentic stores either credential encrypted in the MAXsystem vault and injects the appropriate one per endpoint, keeping the raw token out of agent prompts and logs.

Intent-based discovery

Agents search Jentic for intents like 'send an sms', 'send a transactional email', or 'verify a 2fa code' and receive the matching operation with input schema, ready to execute.

Time to first call

Direct integration: 1-2 days to wire up auth, channel-specific sends, contact management, and balance monitoring across 83 endpoints. Through Jentic: under 30 minutes — only the operations the agent needs are loaded.

FAQs

Specific to using Mensagia API through Jentic.

What authentication does the Mensagia API use?

The API supports two schemes: HTTP bearer authentication via /login and an `api_token` query parameter for simpler scripts. Through Jentic, either credential is held in the encrypted vault and injected at request time so it never enters agent context.

Can I send SMS and email from the same Mensagia API integration?

Yes. Mensagia exposes SMS, email, and voice endpoints under one authenticated session, so the same client can dispatch a transactional SMS and a marketing email without switching credentials or base URLs.

What are the rate limits for the Mensagia API?

The OpenAPI spec does not declare numeric per-second rate limits — throughput is gated by your account balance and channel-specific tier. Use the /balance endpoint to monitor remaining credit before high-volume campaigns.

How do I send an SMS through Jentic?

Run `pip install jentic`, search for `send an sms`, load the SMS send operation, and execute with the recipient phone number and message text. Jentic handles bearer-token injection and returns the message ID for delivery tracking.

Does the Mensagia API support 2FA verification flows?

Yes. Mensagia exposes endpoints to send a one-time code by SMS and verify the code the user submits, which lets sign-in and high-value-transaction flows enforce two-factor authentication without storing OTP state locally.

Is the Mensagia API free?

No. Mensagia operates on prepaid balance — each SMS, email, voice call, and 2FA dispatch consumes credit from your account. Use /balance and /balance/requests to monitor and top up before scaling campaigns.

Mensagia API

Connect the Mensagia API to your agent

Capabilities

Start building with Mensagia API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs