Skip to main content

​
Errors

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

​
Standard error shape

{
  "success": false,
  "message": "Validation failed",
  "errors": [
    "tagString must be between 3 and 64 characters"
  ],
  "timestamp": "2026-03-24T09:01:20.853Z"
}

​
Common statuses

StatusMeaning
400Invalid request body, malformed input, or business validation failure
401Missing or invalid authentication
403Authenticated but not authorized
404Resource not found
409Conflict such as duplicate resources or ambiguous bare tag resolution
422Request is syntactically valid but cannot be processed in the current state
429Rate limit exceeded
500Unexpected server-side failure

​
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.