request_token parameter is required to be sent with every request to the Filter and Risk API endpoints. In order to test Castle without having a client-side integration in place, you can use Test Tokens to evaluate different risk scenarios.
Test Tokens will streamline your testing process by giving you a way to force certain aspects and characteristics of a request, without doing a full integration. For example, if you want to simulate a user using Firefox on a Windows device in the US, you can use the following Test Token value:
Test tokens are only supported on Sandbox environments.
|Pre-determined device combinations to represent various device types
|IP location of the request
|Force a policy action to be returned by Castle
|Set the Castle risk score to a specific value
Mac computer using a Chrome browser, connecting from California, US:
Headless browser, connecting from Japan:
Updated almost 2 years ago