Mock Request Tokens
A 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 Mock Request Tokens to evaluate different risk scenarios.
Format
test|<parameter>:<value>|<parameter>:<value>...
Usage
Mock Request 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 Mock Request Token value:
request_token: "test|device:firefox_on_windows|ip:us-ca"
Reminder
Test tokens are only supported on Sandbox environments.
Test Token Parameters & Values
Parameter | Possible Values | Description |
|---|---|---|
|
| Pre-determined device combinations to represent various device types |
|
| IP location of the request |
|
| Force a policy action to be returned by Castle |
risk | value from | Set the Castle risk score to a specific value |
Examples
Mac computer using a Chrome browser, connecting from California, US:
test|device:chrome_on_mac|ip:us-caHeadless browser, connecting from Japan:
test|device:bot_on_linux|ip:jpUpdated about 2 months ago