Skip to main content

Errors

IDaaS uses structured JSON envelopes for both successful and failed responses.

Standard error shape

Common statuses

Integration guidance

  • Parse both message and errors.
  • Treat 409 and 422 as business outcomes, not only transport failures.
  • Honor Retry-After on 429 responses.
  • Log the timestamp and request identifiers you add client-side.

Retry policy suggestions

  • Retry 429 after the indicated delay.
  • Retry some 5xx responses with backoff.
  • Do not blindly retry 4xx validation or conflict errors.
  • Use idempotency keys for retriable transaction initiation calls.