Community testing tool

VideoID Sandbox Lab

Explore VideoID with your own sandbox credentials. Check document support, tune capture settings, launch a flow, and inspect the exact API requests from one page.

Community tool

This is an independent community tool provided as-is for testing and educational purposes. It is not an official Signicat repository, and it is not endorsed, sponsored, or maintained by Signicat. Use Signicat's public developer documentation as the source of truth for API behavior.

API base ...
Token ...
Redirect URL ...

00

Connection

Add your own sandbox credentials for this browser session. They are not built into the site or shared with other visitors.

How this is used

Client credentials are exchanged for a bearer token. Bearer API token mode sends the pasted token directly in the Authorization header.

How matching is checked

The callback compares this value against `finalResult.personalIdentificationNumber` first, then `finalResult.documentNumber`.


        

01

Supported documents

Load provider coverage first so the numeric `id` values you use in `signicatvideoidConfig.allowedIdTypes` match what the sandbox actually returns.

Available document types

Select the IDs you want to carry into the capture configuration.

Coverage summary

Copy a plain-language summary for support conversations or test notes.

Latest Signicat request

Endpoint, method, and outbound body for the last document lookup.


          

        

02

Capture configuration

Edit the configuration with the generic document types, allowed numeric IDs, and raw JSON visible together.

What these do

`Load config` fetches the saved config for the ID above. `List configs` shows all saved configuration IDs. `Load starter template` fills the form with a local sample so you can tweak it before saving. The presets below quickly apply common test shapes, and if document types are loaded they will also try to fill matching VideoID allowed IDs.

Advanced capture customization

Branding

Visual customization options that are easy to validate quickly in the flow.

Upload Flow

Controls for document capture, upload behavior, and validation screens.

Mobile handover

Settings for moving the flow from desktop to mobile capture.

VideoID native

Native Signicat VideoID-specific tuning and helper notes.

Native camera translations

Add `useNativeCameraButton`, `frontImage.useNativeCameraText`, `backImage.useNativeCameraText`, `selfie.useNativeCameraText`, or document-specific variants inside the `Translations` JSON below.

Action output

This console shows API responses and action outcomes like load, list, save, or validation errors. The Signicat payload preview stays in the JSON preview box above.

Latest Signicat request

Inspect the configuration endpoint and exact JSON body sent to Signicat.


          

        

03

Capture flow

Create a dossier, keep the saved `uiProfile`, and launch the flow with the provider, SDK, process type, and redirect URL you want to test.

Cleanup options

Delete the process first if you want to clean up a single verification run. Delete the dossier when you are finished with the whole test identity.

Latest Signicat request

Use this to verify the capture endpoint and launch payload before following the flow.


          

        

04

API mapping

Quick reference for the API requests this page sends on your behalf.

Document support

`GET /assure/{provider}/document-types` fetches the numeric IDs you can allow.

Configuration

`PUT /assure/capture/configurations/{configurationId}` updates the capture configuration.

Capture launch

`POST /assure/dossiers/{dossierId}/capture` starts the flow and can include `captureParameters.uiProfile`.

Your browser sends these requests using the credentials you provide for this session. If a request fails before Signicat responds, your Signicat setup may need to allow this site as an approved browser origin.