Data Exchange Response Structure

📘

Data Exchange Response Structure

To view the full Email Intelligence Response Structure please visit Data Exchange: Enhanced Detection and API Source Validation (needs Zendesk authentication).

This section includes details about the decryption details of the Data Exchange blob if the customer has sent one to Arkose.

Data Exchange lets Arkose customers pass extra telemetry data as pre-defined parameters and values between their servers and Arkose Labs servers. This happens when a new Arkose session is created. By augmenting the data Arkose Labs already collects with data that only our customers can collect, we can improve the Platform’s effectiveness. The data is sent with each parameter/value pair as an element in an overall JSON structure. It is encrypted with an AES-256-GCM cipher to prevent data tampering.

Arkose Labs must pre-approve all Data Exchange parameters or fields, as well as their allowed values and how they should be interpreted.

Data Exchange provides two major advantages, Enhanced Detection and API Source Validation. Note that even though these features are technically not interdependent (you may use either one or both - or not use Data Exchange at all), we strongly encourage you to use both in conjunction, as they provide additional validation to each other.

• Enhanced Detection uses the additional information from customer parameters to improve the Platform’s detection ability.
• API Source Validation helps ensure that sessions originate from customer page loads. This increases the technical hurdles for attackers trying to directly interact with the Arkose Labs API.