Testing

The IDnow test environment includes a Test Robot, a service that simulates the agent review step automatically, so you can validate your integration end-to-end without human involvement.

note

All test scenarios return a static set of sample data values in the result. The data you send in the identification request (e.g. names, document data) is irrelevant,the Test Robot always returns fixed values for the selected scenario.

Test Scenarios

To trigger a test scenario, set the firstname, lastname, or any one of the custom1–custom5 fields in your Create Identification request to:

{prefix}-{test scenario}

The available scenarios are:

Test scenario	Result status	Result reason
HAPPYPATH	SUCCESS	—
FRAUDIDENT	FRAUD_SUSPICION_CONFIRMED	WARNING_FAKED_MANIPULATED_ID
CANCELED	FAILED	OTHER_ERROR

See Result codes for the full reference of result statuses and reason codes.

Manual Test

A manual test lets you go through the full user-facing flow yourself (web app or mobile app), while the agent review step is handled automatically by the Test Robot.

Prefix: X-MANUALTEST

Steps:

1. Create an identification via the REST API or the user data form, setting firstname, lastname, or a custom field to X-MANUALTEST-{test scenario}.

   firstname: "X-MANUALTEST-FRAUDIDENT"

2. Open the DocIDV web app or mobile app, enter the IdentID, and complete the identification steps.

3. Once you finish in the app, the Test Robot processes the identification automatically. Allow 1–2 minutes for processing.

4. Retrieve the result via the GET Identification endpoint.

VideoIdent tests

Agent video call flows support additional scenarios and the X-AUTOTEST prefix, where both the user and the agent are automated.

Test scenario	Description
CHANGEALLREVIEW	Successful identification; all fields are changed during the review step.
LONGREVIEW	Same as HAPPYPATH, but the review is delayed by 24 hours instead of running immediately.
CHANGEALL	Successful identification, but all fields are changed to new values during the identification (including some non-English UTF-8 characters supported by IDnow).
ABORTIDENT	The agent aborts during the identification (e.g. poor video quality).
FRAUDREVIEW	Identification completes successfully; fraud is detected and confirmed during review. Not supported for eSigning.
FRAUDOK	Agent reports fraud suspicion during the identification, but review marks it legitimate. Not supported for eSigning.
HOLDCERTIFICATE	Successful identification, but signed documents and results are sent 10 minutes after completion. Available only with eSigning identifications.

note

FRAUDIDENT is not supported for eSigning.

Automated Test

When DocIDV is configured to include an agent video call, the Test Robot can simulate both the user and the agent, no manual interaction is required. Use the X-AUTOTEST prefix instead of X-MANUALTEST.

Prefix: X-AUTOTEST

Steps:

1. Create an identification via the REST API, setting firstname or lastname to X-AUTOTEST-{test scenario} — for example X-AUTOTEST-HAPPYPATH.

2. Drive the identification through the standard endpoints:

   1. POST Company Login
   2. POST Create Identification
   3. POST Start Mock Identification

   POST {{TESTROBOTHOST}}/api/v1/startMockIdentification

   For the test environment, {{TESTROBOTHOST}} is https://testrobot.test.idnow.de.

   Headers:

   Content-Type: application/json

   Request body:

   Field	Type	Required	Description
   mobile	string	Yes	Mobile number of the user provided during identification. Example: 015125201203.
   token	string	Yes	The IdentID associated with the identification. Follows the syntax ABC-DEFGH.
   shortname	string	Yes	The shortname your company received from IDnow during account setup, used in the API URL of your requests.

   Example:

   curl -i --location -g 'https://testrobot.test.idnow.de/api/v1/startMockIdentification' \
   --header 'Content-Type: application/json' \
   --data '{
     "mobile": "015125201203",
     "token": "ABC-DEFGH",
     "shortname": "yourshortname"
   }'

3. Once Start Mock Identification has been called, both the user and the agent steps run automatically on the IDnow side. The result is delivered through your configured channel (e.g. webhook) — no further interaction is required.

note

This endpoint currently only supports fully-automated identification for the agent-assisted flow. The identification token passed in the request body must be associated with an identification created with firstname or lastname set to X-AUTOTEST-{test scenario}.

note

X-AUTOTEST only applies when an agent video call is part of your configured flow. For DocIDV integrations without an agent call, use X-MANUALTEST above.

Test with an IDnow Agent

You can request a live test session on the test environment with a real IDnow agent. Contact your account representative or support@idnow.io to arrange a time slot.

caution

Agent-assisted test sessions use IDnow staff time and are billed at hourly rates.