Using the OneSpan Identity Verification API Rapid Proof of Concept

Involved solutions:

• OneSpan Identity Verification

About OneSpan Identity Verification API Rapid Proof of Concept

The OneSpan Identity Verification API Rapid Proof of Concept (IDV API RPOC) is designed to help you evaluate OneSpan Identity Verification by facilitating easy integration of the product workflows into your application.

The IDV API RPOC contains all REST APIs of OneSpan Identity Verification. You can integrate workflows for creating OneSpan Identity Verification transactions, capturing verification results, deleting transaction data, etc. For a full list of available workflows and APIs, see IDV API RPOC Reference.

The use of the IDV API RPOC is limited to 30 days and 400 transactions. The 30-day countdown starts when the email with your credentials to access the IDV API RPOC is sent.

Sign up for the IDV API RPOC

If you want to use the IDV API RPOC to evaluate the integration of the OneSpan Identity Verification workflows, contact the OneSpan Sales team. A member of the Sales team will initiate the sign-up process and help you get started with the IDV API RPOC.

During the sign-up process, you need to provide information to contact your development team. This contact will receive an email with the credentials needed to work with the IDV API RPOC.

Get started with the IDV API RPOC

With the IDV API RPOC, you can integrate all available OneSpan Identity Verification APIs. This article contains instructions to create a JSON Web Token (JWT) and outlines a procedure where you create a transaction, check the verification, and verify the transaction results.

Before you begin

Before you can start working with the IDV API RPOC, you need to create a JSON Web Token (JWT).

To create a JSON Web Token

1. Send the token request to:

   • POST https://gs.onespan.cloud/rpoc-saa/oauth/token

   • Authorization: Basic Authentication

     Provide the username and password from the email you received during the sign-up process (see Sign up for the IDV API RPOC).

   • Body:

     • scope = "tenant_access"

     • grant_type = "client_credentials"

2. Save the token for all future API calls.

Working with the IDV API RPOC

To get started with the IDV API RPOC

1. Create a transaction.

   Send the API request to:

   • PUT https://gs.onespan.cloud/rpoc-saa/api/transaction/

   • Authorization: Bearer jwt_token

   • Body raw, JSON. For more information, see JSON Model.

   Capture the transaction ID, the token, and the role.

2. Verify the transaction on a mobile device.

   In your web browser, navigate to https://gs.onespan.cloud/sales/#/esign/TRANSACTION_ID?access_token=TOKEN

3. Check the verification results.

   Send the API request to:

   • GET https://gs.onespan.cloud/rpoc-saa/api/transaction/TRANSACTION_ID/verification

   • Authorization: Bearer jwt_token

4. Check the transaction results.

   Send the API request to:

   • GET https://gs.onespan.cloud/rpoc-saa/api/transaction/TRANSACTION_ID/document/AuditTrailDocument/pdf

   • Authorization: Bearer jwt_token

Next steps

You can integrate and evaluate further OneSpan Identity Verification workflows. For a list of available workflows and APIs, see IDV API RPOC Reference.