For the complete documentation index, see llms.txt. This page is also available as Markdown.

Bypass Solution

This documentation provides detailed information on generating the required NuData parameter.

How the Solution Works

  1. 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/

  2. 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 result plus input_name.

  3. Attach and send. Put the payload on your own login or checkout request under input_name (usually nds-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/generate

Generate a NuData payload

post

Generates 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.

Authorizations
x-api-keystringRequired
Query parameters
urlstring · uriRequired

The NuData script URL of the target.

Example: https://www.example.com/
session_idstringOptional

The session_id from a previous login call, to continue the same session (login mode only).

Body

Optional JSON body. Omit it for a GET-style call with the default login actions.

checkoutbooleanOptional

Generate a checkout payload instead of a login one (costs 2 requests).

Example: false
click_targetsstring[]Optional

Checkout mode — the elements to click.

proxystringOptional

Proxy for the init flow (optional).

Example: 1.2.3.4:8000:user:pass
Other propertiesanyOptional
Responses
200

The generated payload. In login mode the response carries a session_id to reuse on the follow-up call.

application/json
session_idstringOptional

Login mode — reuse this on the follow-up call to continue the same session.

Example: sess_1a2b…
Other propertiesanyOptional
post/generate

Last updated