Integrations

Integrate what you already have.

Documented platform capabilities for messaging, data, finance and accounts. Specifications and call paths are provided with the installation documentation.

Sending SMS over HTTP

A JSON API, alongside SMPP.

Customers send over SMPP or HTTP(S): both channels share routing, rating, receipts and invoicing. Supplier termination remains SMPP or SS7.

SMPPSMPP 3.4 and SMPP over TLS

HTTP(S)POST /v1/sms with JSON

One lifecyclerouting, receipt, billing, invoice

SuppliersSMPP or SS7 over SIGTRAN

The calls described here belong to the customer’s Auvia installation APIs, not this website. The base address depends on the installation.

Sending: POST /v1/sms

AuthenticationAuthorization: Bearer header with an account API key authorized for sms.send. Each key can have an optional IP allowlist.
IdempotencyWith the optional Idempotency-Key header, the same request received twice within 24 hours returns the same response without sending again.
202 responseThe message is accepted, not delivered. Delivery is established through receipts and status queries.
BatchesUp to 1,000 recipients per request. Each recipient has its own result: an invalid number does not fail the others.
Full rejectionIf all recipients are rejected, the response is 400 or 402, with reasons.

Request fields

frommessage sender
torecipient array, up to 1,000 per request
textmessage text
prioritypriority; the documented example uses otp
validity_minutesmessage validity, in minutes
client_refcustomer reference, returned in webhooks
dlrdelivery receipt request
encodingoptional: auto (default), gsm7 or ucs2
scheduled_atoptional: scheduled sending

Example request, one recipient

POST /v1/sms
Authorization: Bearer <CHIAVE_API>
Idempotency-Key: <VALORE_UNIVOCO>
Content-Type: application/json

{
  "from": "MITTENTE",
  "to": ["<MSISDN_DESTINATARIO>"],
  "text": "Il tuo codice è 482913",
  "priority": "otp",
  "validity_minutes": 60,
  "client_ref": "ordine-8812",
  "dlr": true
}

Example response

HTTP 202
{
  "accepted": 1,
  "rejected": 0,
  "messages": [
    {
      "to": "<MSISDN_DESTINATARIO>",
      "message_id": "<ID_MESSAGGIO>",
      "status": "accepted",
      "parts": 1,
      "encoding": "gsm7",
      "price": 0.045,
      "currency": "EUR"
    }
  ]
}

The API key, number and identifier are placeholders. The price is illustrative, not a rate.

Error codes

Code	HTTP	Meaning
invalid_number	400, per recipient	invalid number or unknown network
missing_text	400	empty text
text_too_long	400	text longer than 10 parts
sender_not_allowed	403, per recipient	unapproved sender
blocked	403, per recipient	firewall or routing rule
insufficient_balance	402	balance exhausted
rate_limited	429	account TPS limit, with a Retry-After header
unauthorized / forbidden	401 / 403	missing or revoked key, or disallowed IP

Stable, documented codes, matching SMPP where possible. The 10-part limit applies to this HTTP API; it does not replace the platform’s other capabilities.

Queries

GET /v1/sms/{message_id}current message status, with per-part detail
GET /v1/balancebalance and credit limit

Webhooks for DLR and MO

DestinationsDelivery receipts (type dlr) and inbound messages (type mo, with from, to, text, received_at and incomplete) arrive by POST at the URL configured on the account.
SignatureX-Signature header: t=<timestamp>,v1=<HMAC-SHA256(secret, t + "." + body)>. The customer rejects signatures older than 5 minutes to limit replay of intercepted notifications.
AcknowledgementAny 2xx response acknowledges receipt of the webhook notification, not delivery of the SMS.
RetriesIf the customer returns an error or does not respond within 10 seconds, retries use increasing delays, up to 8 times in 6 hours. Once retries are exhausted, notification sending stops and the delivery failure is recorded.

Example DLR notification

{
  "type": "dlr",
  "message_id": "<ID_MESSAGGIO>",
  "client_ref": "ordine-8812",
  "to": "<MSISDN_DESTINATARIO>",
  "status": "delivered",
  "parts": 2,
  "parts_delivered": 2,
  "error_code": null,
  "done_at": "2026-10-05T02:27:11Z"
}

Messaging APIs

HTTP(S) SMS APIsending SMS and receiving delivery reports over HTTP/HTTPS
HTTP MNP APIportability information for any MSISDN
Inbound SMS APIreal-time forwarding of MO messages to third-party systems

Data and finance APIs

CDR Export APIexport of call detail records
Finance Document APIaccess to invoices and financial documents
Traffic Report APItraffic reports for any period

REST API for external systems

Balancecurrent balance, credit limit, available amount and currency
Usagemessages, delivered, failed, parts and amounts per period
CDRcall detail records per message
Invoicesnumber, dates, total, amount paid and status
Virtual numberslist, add and remove numbers and ranges
Authenticationtoken with API keys

Protocols

CustomersSMPP 3.4, SMPP over TLS, HTTP(S) API and web portal
SuppliersSMPP 3.4 e 5.0
SS7SIGTRAN (M3UA), through the built-in SMPP-to-SIGTRAN gateway
MNP/HLRDNS ENUM/NAPTR and HTTP(S) MNP API

SMPP 3.4SMPP su TLSSMPP 5.0 (fornitori)SIGTRAN M3UADNS ENUM/NAPTRHTTP(S)SFTP (SS7 records and PCAP)

From protocol to route.

The catalogue describes how incoming traffic is routed, priced and monitored.

Feature catalogue Platform