Skip to main content

Initiating a KYC Screening

Swagger docs:

Screening API endpoints:

To initiate a user screening, first create a screening token by making an HTTP POST request to:


curl --location --request POST '' --header 'Authorization: Bearer {your_access_token}'
{"token": "bf42e9f1-9af8-4a6b-a1fd-9440f1fe9bfd"}

After getting the token, provide it to our javascript widget that you have pasted into your frontend.

Widget source URLs:

Your page should look something like this:

<script src=""></script>
<div id="widgetScreening"></div>
elementId: "widgetScreening",
token: "bf42e9f1-9af8-4a6b-a1fd-9440f1fe9bfd",
redirectUri: "",
externalId: "your-customer-ID",
mode: "Identity",

Initialization properties:

elementIdHTML DOM element that the widget will attach to
tokenscreening token, retrieved as per instructions above
redirectUriyour custom widget redirect URI (optional)
externalIdcustomer ID of the unique user from your system that will reflect on the GlobalPass report (optional)
modeIdentity (identity documents, biometrics, AML) or Address (proof of address, geolocation)

Specifying mode is required if you wish to use Split Flow approach. If Regular Flow is used – do not specify mode. Before starting integration, contact GlobalPass support to find out more about the differences and inform which approach you wish to use, as appropriate set-up on GlobalPass end will be required as well.


Provide the same screening token when initializing both identity and address screenings of the same unique user. This will ensure the two sections, once both completed, will combine on the final screening report.