Method B: Redirect to Verification

Responses

🟢200Success

text/html

Response Behavior

When this endpoint is called, the API's behavior is as follows:

You will receive an HTTP 200 OK response.

The response body will contain raw HTML content for a loading page (e.g., <html>...</html>)

The actual redirection to the verification session does not occur via a standard HTTP 302 redirect or a Location header. Instead, the user's browser is redirected through embedded logic and a series of redirect chains handled by the verification service.

How to Obtain the Redirect URL

To correctly redirect your user to the iDenfy verification session, you must capture the final URL from the network redirect chain. This URL is not available in the initial response body or headers. It can be captured using browser developer tools or a network inspection proxy.

Example Flow
The network flow will look similar to this:

Initial Request:

GET https://partner-api-stage.p100.io/v1/kyc/verification/6ef2fb57.../1306fc1d...

Final Redirect URL (Target):

GET https://ui.idenfy.com/?authToken=wosP8TruRQm...&country=de

To properly redirect your user, you must use the final URL from this chain.

Important Notes
If you test this endpoint in tools like Apidog or Postman, you will see the raw HTML of the initial loading page in the response body.

Do not attempt to copy and open this HTML content directly in a browser, as it will not work.

You must capture the final redirect URL from the network flow and use that URL to redirect your user.

🟠404P412: User not exist

🟠404P445: KYC not found

🟠400P500: Unknown exception

🟠400P501: Service temporarily unavailable

🟠400P459: User not verified

<!doctype html> <html lang="en"> <head> <meta charset="utf-8"> <title>iDenfy</title> </head> <body id="body"> <ivs-root> </ivs-root> <script src="runtime...js" type="module"></script> <script src="main...js" type="module"></script> </body> </html>