Onurix API

Name: Onurix API
Brand: Onurix API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsSms MessagingapiKey9 EndpointsREST

For Agents

Send SMS messages, trigger 2FA verification codes, and shorten campaign URLs through a single API. Useful for agents that need to deliver one-off transactional messages or verify a phone number.

Install Jentic One Beta

Connect the Onurix API to your agent

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

Send transactional SMS messages to a phone number with custom sender ID

Trigger and verify 2FA one-time passcodes over SMS

Block phone numbers from receiving further SMS sends

Shorten long URLs and retrieve click statistics for the shortened link

GET STARTED

Start building with Onurix API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Onurix API, keeping it validated and agent-ready. Onurix is a Spanish-language messaging platform that exposes a REST API for sending SMS, WhatsApp messages, voice calls, and 2FA verification codes, plus URL shortening with click analytics. The same API also supports event-ticket workflows where a confirmation SMS is sent to attendees and the ticket is later validated at the door. The surface is small (nine endpoints) and oriented around one-shot sends rather than long-running campaigns.

Use Cases

Patterns agents use Onurix API for, with concrete tasks.

★ SMS Two-Factor Authentication

Add SMS-based 2FA to a sign-in flow by sending a one-time code to the user's phone and verifying their input. Onurix exposes a paired send-and-verify pair of endpoints so the application does not need to store or hash the code locally. Suitable for low-volume consumer apps that want SMS 2FA without standing up a dedicated verification provider.

Call POST /2fa/send-sms with the user's mobile number, then call POST /2fa/verification-code with the code they entered and return whether verification succeeded.

Event Ticket Confirmations

Send an SMS confirmation to attendees when a ticket is purchased and validate the ticket at the venue using a state-change call. The flow uses POST /show-send-sms for delivery and POST /show-state-change for entry validation, eliminating the need for a separate ticketing-platform integration for small events.

Send an event ticket SMS to +34600000000 for show ID SHOW123, then mark that ticket as used when the attendee arrives.

Campaign Link Shortening with Analytics

Shorten a long marketing URL and pull click statistics back to measure campaign performance. POST /url/short returns the short link and POST /url/short-statistic returns the click count, so an agent can stage a campaign and report on it from the same API surface.

Shorten https://example.com/promo-summer-2026 and return the click count for the resulting short link 24 hours later.

AI Agent SMS Notifications

Let a Jentic-orchestrated agent send a transactional SMS without holding the raw API key. The agent searches for a send-SMS operation, Jentic injects the credential at execution time, and the message is delivered through Onurix while the agent only ever sees a scoped token.

Search Jentic for 'send a transactional SMS', load the Onurix send-sms schema, and execute it for phone number +34600000000 with body 'Order #1234 confirmed'.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/send-sms

Send a transactional SMS message

POST

/2fa/send-sms

Send a 2FA verification code over SMS

POST

/2fa/verification-code

Verify a 2FA code submitted by a user

POST

/url/short

Create a shortened URL

POST

/url/short-statistic

Retrieve click statistics for a short URL

GET

/balance

Get the current account balance

POST

/block-phone

Block a phone number from receiving SMS

POST

/send-sms

Send a transactional SMS message

POST

/2fa/send-sms

Send a 2FA verification code over SMS

POST

/2fa/verification-code

Verify a 2FA code submitted by a user

POST

/url/short

Create a shortened URL

POST

/url/short-statistic

Retrieve click statistics for a short URL

Why Jentic?

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

Credential isolation

The Onurix account credential is stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped execution token at runtime — the raw credential never enters the agent's context window or logs.

Intent-based discovery

Agents search Jentic with intents like 'send a 2FA SMS' or 'shorten a campaign URL' and receive the matching Onurix operation with its input schema, so the agent can call the right endpoint without reading the docs.

Time to first call

Direct Onurix integration: 1-2 days to build the auth handshake, balance check, and retry logic. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Onurix API through Jentic.

Why is there no official OpenAPI spec for Onurix API?

Onurix does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Onurix 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 Onurix API use?

The spec does not declare a security scheme; the live API uses an account credential that callers pass with each request. When called through Jentic, the credential is held in the Jentic vault and a scoped token is injected at execution time so the agent never sees the raw value.

Can I send WhatsApp or voice calls with the Onurix API?

The published spec exposes SMS, 2FA SMS, event-ticket SMS, URL shortening, and account balance. WhatsApp and voice are described in Onurix's product literature but are not in the current 9-endpoint spec, so an agent should treat this surface as SMS-only until those endpoints are added.

What are the rate limits for the Onurix API?

Onurix does not document a public rate-limit ceiling in the spec. Sends are gated by the account balance returned from GET /balance, so an agent should check the balance before high-volume runs and back off on any 429 response.

How do I send a 2FA code with the Onurix API through Jentic?

Run pip install jentic, then search for 'send a 2FA code over SMS'. Jentic returns the POST /2fa/send-sms operation; load its schema, call it with the destination phone number, and follow up with POST /2fa/verification-code to validate the code the user enters.

Is there a free tier for the Onurix API?

Onurix sells SMS credit by package; there is no published free tier in the spec. GET /balance returns the remaining credit on the account so an agent can confirm there is enough budget before issuing sends.

Onurix API

Connect the Onurix API to your agent

Capabilities

Start building with Onurix API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs