Skip to main content

Support

Before you contact us​

Most integration questions are answered by:

  • Error Handling — what each status code means and when to retry
  • The shared error model — the detail field of an error response usually names the exact problem
  • Verification Integration Guide — what every failureReason means
  • The search box (top right) — all endpoints, schemas, and error codes are indexed

Contact the platform team​

For staging credentials, production host details, trust network membership changes, webhook configuration, or anything else account-specific, contact the iDen2 platform team:

What to include in a support ticket​

Help us help you fast — include:

  1. Service and endpoint — e.g. Verification Gateway POST /api/v1/verifier/sessions
  2. Environment — staging (*.stg.iden2.app) or production
  3. Identifiers — offerId / sessionId, your externalId, and (for trust issues) any issuerMemberId
  4. Timestamps — when the request was made (ISO 8601, with timezone)
  5. The full Problem Details body — especially type, detail, instance, and serviceVersion
  6. What you expected vs. what happened
Never include secrets

Don't paste your password, Authorization header, VP tokens, or qrCodeDataUrl / offerUrl / authorizationUrl values into tickets.

Requesting changes​

  • Trust network — to trust an additional issuer or register as one, include the relevant member details and your trustNetworkId.
  • Configuration — credential types, presentation definitions, TTL caps, and webhook endpoints are configuration-managed; request changes through the platform team.