Skip to main content

​
What are session statuses?

Verification session statuses indicate the progress of the verification session, indicating the stage where the session currently is. Helium ID notifies you about the following stages, sending a descriptive label and a numerical status code:
  • not started (1001)
  • started (2000)
  • abandoned (3033)
  • completed (2001)
  • successful (2010)
  • failed (4100)
  • cancelled (5000)

​
Fetch session status

The session status is available in the status and statusCode properties in:
  • The decision webhook payload
  • The GET /v1/verifications response
  • The GET /v1/verifications/{id} response

​
Verification session status codes

The session status codes indicate the progress of the verification session, signaling the stage where the end-user’s verification process currently is. This information is returned as strings for the status and numbers for the statusCode.
StatusCodeSent viaWhat does this mean?
not started1001APIA session has been created for the end-user. They have not yet entered the verification flow.
started2000Webhook / APIThe end-user has started their session and landed in Helium ID’s verification flow. No decision is available yet.
abandoned3033Webhook / APIVerification has been abandoned because the end-user started the verification session but never finished it (a session is abandoned 7 days after being created unless it gets a conclusive decision before that). The verification process is complete.
completed2001Webhook / APIEnd-user’s required data has been submitted and processed.
successful2010Webhook / APIPositive: end-user was verified. The verification process is complete.
failed4100Webhook / APINegative: end-user has not been verified. The verification process is complete. Either it was a fraud case or some other severe reason that the end-user could not be verified. You should investigate the session further.
cancelled5000Webhook / APIThe verification session was explicitly cancelled before it could be completed.
Responses 2010, 4100, 3033 and 5000 are conclusive responses. The session is closed and the session URL is no longer available for the end-user to try again. If you decide to give the end-user another try after a conclusive response, you need to create a new session using the POST /v1/verifications endpoint.

​
About verification session expiry

All verification sessions expire after 7 days.
  • Sessions in the not started status will move to cancelled
  • Sessions in the started status will move to abandoned