Skip to main content
Akamai’s web protection expects 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 for you. Host: web.veilroute.dev 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 cookies field.
  • Send the follow-up request from the same clean session and egress IP you used to obtain them.
  • Carry the cookies VeilRoute returns forward onto your next request.
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 those cookies.
3

Submit the sensor

Post the returned sensor_data to the site and keep the updated cookies for the next call.