Arkose Connector

Arkose is a bot and fraud prevention platform that uses enforcement challenges. These challenges are not static like traditional CAPTCHAs—they are context-based and dynamic, making them resistant to automation and AI.

Use the Arkose connector to integrate Arkose's bot and fraud prevention capabilities into your flow. This connector lets you trigger Arkose Enforcement Challenges whenever a user interacts with specific elements in a flow screen.

Setting Up the Arkose Connector

To integrate the Arkose connector, follow the steps below:

Navigate to Connector

• Visit the Connectors page in the Descope Console.
• Choose Arkose from the list of connectors.

Connector Setup

Set up the necessary inputs:

• Connector name: Assign a custom name for your connector, especially useful when using multiple connectors originating from the same template.
• Connector description: (Optional) A brief description of your connector's purpose.
• Public Key: The Arkose public key, that can be found on the Keys screen in the Arkose portal.
• Private Key: The Arkose private key, that can be found on the Keys screen in the Arkose portal.
• Client API Base URL: (Optional) A custom base URL to use when loading the Arkose API script. If not provided, the default value of https://client-api.arkoselabs.com/v2 will be used.
• Verify API Base URL: (Optional) A custom base URL to use when verifying the session token using the Arkose Verify API. If not provided, the default value of https://verify-api.arkoselabs.com/api/v4 will be used.

Test & Save

• Validate your configuration by clicking the Test button and observing the Test Results section.
• Conclude the setup process by selecting Create.

Implementing the Arkose Connector in Your Flow

Integration

Click on the blue plus sign inside the flow builder and choose "Connector". You should be able to see the new connector action as shown below:

This flow shows an example where the user needs to complete the Arkose challenge on the Welcome screen to proceed:

In the flow, go to the screen you want to protect and in the Actions section, select the Arkose connector. This will trigger the Arkose challenge whenever the user interacts and tries to proceed to the next step.

How Enforcement Works

When the Arkose connector is active on a screen, any button that attempts to move the user forward will be subject to Arkose validation. If Arkose detects suspicious or high-risk signals, it automatically presents the user with a challenge (puzzle) before allowing them to proceed.

If the challenge fails, Arkose will return with validation failed, and the end user will be blocked from moving to the next step in the flow.

If the challenge succeeds, the user can continue normally onto the next screen without interruption.

Testing the Arkose Connector

If you would like to simulate a high risk scenario and trigger the Arkose challenge prompt, you can do this by following the steps below:

To test the challenge behavior:

1. Open Chrome DevTools.
2. Go to the Network Conditions tab (or via Command Menu → “Network conditions”).
3. Change your User Agent to: challengeme
4. Retry the flow action.

This forces Arkose to present a challenge so you can confirm that the connector is working end-to-end.