Session Handling

A key part of API integration is handling sessions properly - session keys will be required across the entire user flow. A unique sessionKey can be created utilizing the POST /v1/verify/session endpoint. This sessionKey will then be used for a variety of user verification steps as well as the final submission of a transaction.

Relevant Endpoints

Device Biometrics

Identity and Document Verification

Submitting a Transaction


Session keys are required for proper integration!

Many of the Noba POST endpoints require a unique sessionKey. It is critical that sessionKeys remain consistent across a single user flow.