Altiria API

Name: Altiria API API
Brand: Altiria API
Availability: InStock

★ Only Publicly Available SpecCommunicationsSms Messagingbasic11 EndpointsREST

For Agents

Send SMS, email, voice, and WhatsApp messages and manage WhatsApp conversations through 11 HTTP Basic-authenticated endpoints. Useful for agents handling notifications, OTPs, and customer-care messaging in Spanish-speaking markets.

Quickstart

Get started with Altiria API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send an SMS with Altiria"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Altiria API API.

Send transactional and marketing SMS messages via POST /sms

Look up the delivery status of a sent SMS by id with GET /sms/{id}

Send transactional emails through POST /mailing

Send text-to-speech voice messages with POST /voice and pre-recorded audio with POST /voiceAudio

Send SMS messages that link to a hosted landing page via POST /landingsms

GET STARTED

Start building with Altiria API API

Explore with Jentic

View OpenAPI Spec

Use for: Send a transactional SMS to a customer, Look up the delivery status of an SMS by id, Send a one-time-password email to a user, Make a voice call that reads out a generated message

Not supported: Does not handle inbound voice IVR call control, push notifications, or chat-widget hosting — use for sending SMS, email, voice, WhatsApp, and SMS-with-landing-page messages only.

Jentic publishes the only available OpenAPI specification for Altiria API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Altiria API, keeping it validated and agent-ready. Altiria is a Spanish business-messaging platform that provides programmatic access to SMS, email, voice, WhatsApp, and SMS-with-landing-page channels through 11 HTTP Basic-authenticated endpoints. Teams use it to send transactional notifications, OTPs, and marketing campaigns across channels, and to manage two-way WhatsApp conversations. The API targets Spanish-speaking markets with strong coverage across Iberia and Latin America.

Use Cases

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

★ Multi-Channel Transactional Notifications

Operations teams route order confirmations, shipping updates, and OTPs across SMS, email, voice, and WhatsApp from a single Altiria account. Because the channels share an account and an HTTP Basic credential, the integration is one credential plus a small dispatcher that picks the channel based on the customer's preference. Delivery status for SMS is exposed via GET /sms/{id}.

POST /sms with destination phone, message body, and sender id, then poll GET /sms/{id} until status is delivered or expired.

Two-Way WhatsApp Customer Care

Customer-care teams use the WhatsApp endpoints to receive inbound messages and reply within the WhatsApp 24-hour window from their existing helpdesk. Altiria exposes conversation listing, message retrieval, and reply-send endpoints, so a helpdesk integration can render full conversation threads alongside the customer's record.

Call GET /whatsapp/conversations/{from}/{to}/messages to fetch the open conversation, then POST a reply to /whatsapp/conversations/{from}/{to}/messages.

SMS-with-Landing-Page Marketing

Marketing teams send SMS messages that include a short link to a hosted, personalised landing page via POST /landingsms. The landing page captures clicks and conversions tied back to the campaign, which lets Altiria report on engagement without the team standing up tracking infrastructure of their own.

POST /landingsms with destination phone, body text, and the landing-page template id, then read the campaign report to count clicks.

AI Agent Messaging Workflows via Jentic

An AI customer-care agent built on Jentic can take 'send an order confirmation by WhatsApp, fall back to SMS' and resolve it to the WhatsApp template send and SMS send in sequence. The HTTP Basic credential stays in the MAXsystem vault and is injected only at call time.

Search Jentic for 'send a WhatsApp template message', load the POST /whatsapp schema, execute it; on failure, fall back to POST /sms with the same body.

Key Endpoints

11 endpoints — jentic publishes the only available openapi specification for altiria api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/sms

Send an SMS message

GET

/sms/{id}

Get SMS delivery status by id

POST

/mailing

Send a transactional email

POST

/voice

Send a text-to-speech voice message

POST

/voiceAudio

Send a voice message from a pre-recorded audio file

POST

/landingsms

Send an SMS that links to a personalised landing page

POST

/whatsapp

Send a WhatsApp template message

POST

/whatsapp/conversations/{from}/{to}/messages

Send a message within an active WhatsApp conversation

POST

/sms

Send an SMS message

GET

/sms/{id}

Get SMS delivery status by id

POST

/mailing

Send a transactional email

POST

/voice

Send a text-to-speech voice message

POST

/voiceAudio

Send a voice message from a pre-recorded audio file

POST

Why though Jentic?

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

Credential isolation

Altiria HTTP Basic credentials are stored encrypted in the Jentic vault (MAXsystem). Agents only see a runtime-injected Authorization header at execution and never hold the raw login or password.

Intent-based discovery

Agents search Jentic by intent (e.g., 'send an SMS', 'send a WhatsApp template') and Jentic returns the matching Altiria operation with its schema, so the agent doesn't need to know which channel maps to which endpoint.

Time to first call

Direct Altiria integration: half a day to a day for auth, channel-specific payloads, and delivery-receipt handling. Through Jentic: under an hour to search, load, and execute the first send.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio API

Global multi-channel messaging with broader country coverage and richer programmable voice

Choose Twilio when the workflow spans many countries beyond Iberia and Latin America or needs deep IVR and programmable voice features.

Alternative

MessageBird API

European multi-channel messaging with strong WhatsApp and Voice presence

Choose MessageBird when European compliance, broader Bird Flow Builder features, or richer Conversations API tooling is preferred.

Complementary

SendGrid API

Dedicated transactional email at higher volume than Altiria's email channel

Use SendGrid alongside Altiria when email volume is high and the team wants email-specific deliverability tooling, while keeping Altiria for SMS and WhatsApp.

FAQs

Specific to using Altiria API API through Jentic.

Why is there no official OpenAPI spec for Altiria API?

Altiria does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Altiria API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Altiria API use?

Altiria uses HTTP Basic authentication with an account login and password issued from the Altiria dashboard. Through Jentic, those credentials are stored encrypted in the MAXsystem vault and the Authorization header is injected at call time, so they never enter agent prompts.

Can I send a WhatsApp template through the Altiria API?

Yes. POST to /whatsapp with the destination number, the approved template id, and any template parameters. To follow up inside the 24-hour conversation window, POST to /whatsapp/conversations/{from}/{to}/messages.

What are the rate limits for the Altiria API?

Specific per-account limits are not in the spec. Treat the API as account-throttled and add retry-with-backoff for 429 responses. For high-volume SMS campaigns, contact Altiria to confirm your tier's burst and steady-state ceilings.

How do I send an SMS through Jentic?

Run pip install jentic, then search with 'send an SMS via Altiria'. Load the POST /sms schema, fill in destination, message body, and sender id, and execute. Jentic handles the Basic auth header from the vaulted credential.

Does the Altiria API support delivery receipts for SMS?

Yes. After POST /sms returns an id, call GET /sms/{id} to read the current delivery status. For high-volume use, configure delivery webhooks in the Altiria dashboard to avoid polling.