Quickstart · ~5 minutes
From zero to your first resolved address.
Authenticate, register a channel, call one endpoint, read the verdict — one deterministic engine, two API groups, sub-50ms.
acme trading ltdLONDON??u.k.
<Nm> Acme Trading Ltd<TwnNm> London<Ctry> GB
✓ REPAIRED · sub-50ms · rule_source EPC153-22 §4
Four steps to live01 — 04Every call inherits your channel defaults.
1Get credentialsTwo factors per call — an OAuth bearer token and an X-API-Key. Register an app for test keys (sandbox) and live keys (production).
2Register a channelSet scheme, direction, output mode and thresholds once; every later call reuses them via channelName.
3Pick your scopeFixing a stored address? Call the Party Address API. Fixing a payment message? Call the Message Address API. Same verbs, two scopes.
4Read the statusCOMPLIANT / NOT_COMPLIANT on a check; VALIDATED / REPAIRED / PARTIALLY_REPAIRED / NOT_REPAIRED on a convert — with a reason code on every miss.
Your first callStructurally check one address — no postal DB, sub-100ms.
# Your first call - structurally check one address
curl -X POST https://sandbox.ionova.io/ars/v4/check-party-address \
-H "Authorization: Bearer $TOKEN" -H "X-API-Key: $ARS_KEY" \
-H "Content-Type: application/json" \
-d '{"postalAddress":{"country":"DE","townName":"Berlin"}}'
Why it matters — from 15 November 2026 both SWIFT CBPR+ (SR2026) and EPC SEPA begin rejecting — not flagging — any payment whose address lacks a structured town and country. ARS returns a corrected, transmit-ready address in a single call, every fix citing a regulatory rule_source.