Authentication
Two factors on every call.
Every request carries an OAuth bearer token and an X-API-Key. Generate both yourself — test keys for the sandbox, live keys for production.
The two factorsSent on every endpoint, EP-01 through EP-27.
| Factor | Header | What it is |
|---|---|---|
| Bearer token | Authorization: Bearer <token> | Short-lived OAuth access token that identifies the caller. |
| API key | X-API-Key: <key> | Long-lived account key that scopes the call to your subscription. |
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"}}'
Get your keysSelf-service, from the developer dashboard.
1Create an accountRegister, then sign in to the developer portal. Your session unlocks the application and credentials screens.
2Register an applicationCreate an app to represent your integration. ARS issues a client credential pair scoped to it.
3Copy your X-API-KeyGrab the sandbox key first. Promote to a live key when you are ready for production traffic.
4Exchange for a tokenUse your client credentials to mint a short-lived bearer token, then call any endpoint.
Sandbox vs live — the sandbox base URL is https://sandbox.ionova.io/ars/v4; production is https://api.ionova.io/ars/v4. Test keys only resolve against the sandbox. Rotate or revoke a key at any time from the application screen — in-flight tokens expire on their own short TTL.