Download OpenAPI specification:Download
https://api.signicat.com/reuseid/The Signicat ReuseID Onboarding API enables you to implement your own reusable identity through onboarding or step-up operations. With this API, you can:
This REST API uses the OAuth 2.0 protocol for authorisation. All request and response bodies are formatted in JSON.
Before you can start making requests to this API, you need to learn how to connect to it. To do this, see the Connect to Signicat APIs Quick start guide.
Use the Signicat Audit logs service to see documented evidence of the sequence of activities that have affected a system.
When you make an API call to Signicat and an error occurs, you will receive a response message with an error code.
Use the Signicat Events service to automatically receive information about when something happens in one of our services into your system.
Note: This is often referred to as callback.
The ReuseID Onboarding API provides you with operations related to the onboarding flow, such as starting and getting information about a ReuseID session.
The Start onboarding endpoint initiates an onboarding session.
In this flow, you will:
| externalRef | any |
| provider | string A parameter to specify which identify proofing provider to use. The current two providers available are |
object An object that contains parameters for deciding what kind of documents can be used, and which document should be the default.
Note: When multiple |
{- "externalRef": "Empl10300469",
- "provider": "signicatvideoid",
- "videoidProviderOptions": {
- "docType": 138,
- "docTypes": [
- 138,
- 123
], - "defaultId": 138
}
}{- "data": {
- "status": "Pending",
- "transactionId": "94099e7e-b391-45fb-9404-b54682f16d03",
- "userId": "7f1994f0-5fed-4e0f-a8e2-64da520a09cb",
- "activationCode": "2005468691",
- "dossierId": "41ff5755-4ece-42cf-b7de-3efd0181ba88",
- "processId": "8be8325a-9654-4165-a56f-0d1ccdc3bd3e"
}
}The Get onboarding endpoint gets data from an onboarding session.
| transactionId required | string The ID of the transaction, given in the Start onboarding session. |
| transactionId | string The ID of the transaction, given in the Start onboarding session. |
{- "data": {
- "transactionId": "e35ebbf7-9631-4966-9762-ae939c80eda1",
- "userId": "a1e26081-35b4-4557-a46a-ef50bc91672f",
- "activationCode": "8954685641",
- "deviceId": "b1g73121-55c4-9238-l39j-ek60dc91872g",
- "proofingId": "30745db7-4403-4403-aa7e-cb35435ee565",
- "dossierId": "3d563ac4-9d26-4a6a-b58d-5a29cacfe015",
- "processId": "2f54b0a4-1a77-42e2-98d8-369116ef2055",
- "status": "Completed",
- "userData": {
- "firstName": "JANE",
- "lastName": "SMITH",
- "dateOfBirth": "1990-01-01",
- "gender": "F",
- "nationality": "NOR"
}
}
}The ReuseID Step-up API provides you with operations related to the step-up flow, such as starting and getting information about a ReuseID step-up session.
The Start step-up endpoint initiates a step-up session.
In this flow, you will:
| userId required | string Example: "0eb66632-88d0-4ef4-8126-495c64a0abd2" The ID of the user that will carry out the operation, in a valid UUID format. |
| deviceId required | string Example: "f8d74181-9e00-41ba-ba4f-43aa6a3dfea5" The ID of the end-user's device that will be used for the operation. |
| provider | string A parameter to specify which identify proofing provider to use. The current two providers available are |
object An object that contains parameters for deciding what kind of documents can be used, and which document should be the default.
Note: When multiple |
{- "userId": "0eb66632-88d0-4ef4-8126-495c64a0abd2",
- "deviceId": "f8d74181-9e00-41ba-ba4f-43aa6a3dfea5",
- "provider": "string",
- "videoidProviderOptions": {
- "docType": 138,
- "docTypes": [
- 138
], - "defaultId": 138
}
}{- "data": {
- "status": "Pending",
- "transactionId": "0160e8b9-dabc-4a16-b995-29d88e6f102f",
- "userId": "0eb66632-88d0-4ef4-8126-495c64a0abd2",
- "deviceId": "f8d74181-9e00-41ba-ba4f-43aa6a3dfea5",
- "dossierId": "e73801d2-3e7f-4184-8fda-67cc3b03416d",
- "processId": "0dca14cf-957d-46d9-b374-520f9c650859"
}
}The Get step-up endpoint gets data from a step-up session.
| transactionId required | string The ID of the transaction, given in the Start step-up session. |
| transactionId | string The ID of the transaction, given in the Start step-up session. |
{- "data": {
- "transactionId": "e35ebbf7-9631-4966-9762-ae939c80eda1",
- "userId": "a1e26081-35b4-4557-a46a-ef50bc91672f",
- "deviceId": "b1g73121-55c4-9238-l39j-ek60dc91872g",
- "proofingId": "30745db7-4403-4403-aa7e-cb35435ee565",
- "dossierId": "3d563ac4-9d26-4a6a-b58d-5a29cacfe015",
- "processId": "2f54b0a4-1a77-42e2-98d8-369116ef2055",
- "status": "Completed",
- "userData": {
- "firstName": "JANE",
- "lastName": "SMITH",
- "dateOfBirth": "1990-01-01",
- "gender": "F",
- "nationality": "NOR"
}
}
}