sensor_data computed by the browser and tied to the session’s
cookies (_abck, bm_sz). A plain HTTP client never produces it, so the request is challenged.
VeilRoute computes that sensor — and the related challenge payloads — for you.
Host: web.veilroute.dev
Point us at the page
CallPOST /api/v1/sensor with the target page url and your
cookies — VeilRoute runs the matching Akamai runtime and returns the sensor. New targets are added
on request; ask on Discord.
For Smiles Argentina (smiles.com.ar), which uses Akamai’s SBSD challenge instead of the
_abck sensor, use the sbsd method — pass the page’s vid, bm_o, userAgent
and url, and post the returned body to the site’s SBSD collector.
Methods
Sensor
sensor_data for the _abck browser challenge.sbsd
The
sbsd body some sites expect alongside the sensor.sec-cpt
Solves the
sec-cpt proof-of-work challenge.pixel
Builds the Akamai pixel payload.
parse
Reads the script constants from a bootstrap script.
Session- and cookie-bound
The web sensor is tied to the session it was generated for. For best results:- Pass the cookies you already hold for the target site in the
cookiesfield. - Send the follow-up request from the same clean session and egress IP you used to obtain them.
Unlike the mobile (BMP) sensor, the web sensor is not IP-independent. Rotating the IP between
getting the sensor and sending the request lowers your success rate.
Typical flow
1
Collect your cookies
Make your initial request to the target site and capture its
_abck / bm_sz cookies.2
Request a sensor
Call
POST /api/v1/sensor with the page url and those cookies.3
Submit the sensor
Post the returned
sensor_data to the site, solving any sec-cpt / sbsd / pixel
step it asks for with the matching method.