Bypass Solution
This documentation provides detailed information on generating the required NuData parameter.
How the Solution Works
Find the sensor script. Identify the NuData script URL the page loads, for example
https://nudata.ticketmaster.com/2.2/w/w-481390/sync/js/,https://fc.kohls.com/2.2/w/w-756138/sync/js/ , https://src.mastercard.com/nudetect/2.2/w/w-802323/sync/js/Generate with one call. Send that URL to the Takion NuData endpoint. We load the site's NuData settings, generate a valid payload server-side, and return
resultplusinput_name.Attach and send. Put the payload on your own login or checkout request under
input_name(usuallynds-pmd) and continue as normal. No browser runs on your side at any point.
Endpoint
The endpoint lives on the Castle subdomain:
https://nudata.takionapi.tech/generateGenerates the NuData behavioral payload for the target. url and session_id are query parameters; the simulated actions, cookies, proxy and checkout options go in the JSON body. GET also works (with the default login actions). Login mode is session-based — the first call returns a session_id; send it back to continue. Checkout mode (checkout: true) costs 2 requests instead of 1.
The NuData script URL of the target.
https://www.example.com/The session_id from a previous login call, to continue the same session (login mode only).
Optional JSON body. Omit it for a GET-style call with the default login actions.
Generate a checkout payload instead of a login one (costs 2 requests).
falseCheckout mode — the elements to click.
Proxy for the init flow (optional).
1.2.3.4:8000:user:passThe generated payload. In login mode the response carries a session_id to reuse on the follow-up call.
Login mode — reuse this on the follow-up call to continue the same session.
sess_1a2b…Missing/invalid input or an expired/invalid session.
Authentication or quota failure — HTTP 401 with an error message.
Generation failed, or an unexpected error.
POST /generate?url=https%3A%2F%2Fexample.com HTTP/1.1
Host: nudata.takionapi.tech
x-api-key: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 265
{
"actions": [
{
"type": "input",
"name": "password-input",
"value_length": 8,
"ANY_ADDITIONAL_PROPERTY": "anything"
}
],
"checkout": false,
"click_targets": [
"text"
],
"cookies": {
"ANY_ADDITIONAL_PROPERTY": "text"
},
"proxy": "1.2.3.4:8000:user:pass",
"ANY_ADDITIONAL_PROPERTY": "anything"
}{
"session_id": "sess_1a2b…",
"ANY_ADDITIONAL_PROPERTY": "anything"
}Last updated