For developers · REST API

From zero to first API call in five minutes

The integrator's front door: a five-minute Quick Start, full reference for all 24 endpoints, authentication, the 30-code reason catalogue, and a production-shaped sandbox. It turns a regulatory deadline into a delivery plan you can run in days.

Get API keys Read the Quick Start

The ARS Developer Portal is the integrator's front door: a five-minute Quick Start, full reference for all 24 endpoints across five layers, authentication and security, the 30-code reason catalogue, and a production-shaped sandbox.

Quick Start

A first call in five minutes

Sign up & generate an API key

Per-tenant key, issued instantly.

Point at the base URL

https://api.ionova.ai/v4.4

POST a message

Hit the AutoCorrect endpoint with a channelName.

Read back the result

The corrected ISO 20022 message and its status.

# One channelName + payload — scheme, direction, format & corridor
# all come from the registered Channel Profile.
curl https://api.ionova.ai/v4.4/convert-message-party-addresses \
  -H "Authorization: Bearer $ARS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "channelName": "SCT_OUT", "message_xml": "<...pain.001...>" }'

API surface

24 endpoints across 5 layers

Fully documented with request/response schemas and worked examples.

PreCheck

Sub-100ms structural validation.

AutoCorrect

Message-level — returns the complete corrected XML.

Batch

Up to 1,000 sets or 100 messages per call.

Message-level

Whole-message AutoCorrect with XPath write-back.

R-transactions

Dedicated endpoints applying the EPC §8.3 pass-through exemption.

Auth & security

Defence in depth

Per-tenant API keys, RFC 9421 HTTP Message Signatures, and JWT — with strict per-tenant isolation.
Data-sovereign deployments — runs on-premise, in a private VPC, or air-gapped; no PII need leave the institution.

Reason codes

30-code catalogue

Every non-compliant or repaired response carries structured reason codes, each mapped to the regulatory rule_source it maps to. Downstream systems route by code prefix without parsing free text.

Content area	What you find there
Quick Start	First call in five minutes
API Reference	All 24 endpoints, schemas, examples
Authentication	Keys, signatures, JWT, isolation
Reason Codes & Status	30 codes, four-state taxonomy
Editions & Channels	Edition matrix, channel comparison
Operate	Cutover mechanics, go-live checklist, support tiers

Sandbox & go-live

From first call to production

Production-shaped sandbox

Call real endpoints with sample data before writing client code — most pilots are calling sandbox endpoints by week 4.

Go-live checklist

A numbered checklist, signed off by security review, takes you from first call to production.

No breaking changes in v4.4

v4.4 preserves the v4.0 issues[] array alongside the v4.2 reasons[] array — backwards-compatible.

FAQ

Frequently asked questions

About five minutes via the Quick Start — sign up, get a key, POST a message, read the corrected response.

Per-tenant API keys plus RFC 9421 HTTP Message Signatures and JWT, with strict per-tenant isolation.

Yes — a production-shaped sandbox with sample data. Most pilots call sandbox endpoints by week 4 and can validate behaviour with no client code via the Playground.

No. v4.4 is backwards-compatible: the legacy issues[] array is preserved alongside the newer reasons[] array.