Read the AdsLab task feed and normalise it
The endpoint is a path, not a query string, and the field names change per task type. Normalising once at the edge keeps the rest of your site from caring.
Task APIs, signed postbacks, offerwall SDKs and the integration details the docs get wrong.
9 entries
The endpoint is a path, not a query string, and the field names change per task type. Normalising once at the edge keeps the rest of your site from caring.
It is sha256 of the transaction id, a hyphen and your Security Hash — not the Publisher API key their integration page names.
Dedupe on the transaction id, answer 200 to everything, and treat a reversal as the full chain — user credit and referral commission both.
Their postbacks come from one address. Enforcing it is free — unless you are behind Cloudflare, where REMOTE_ADDR is Cloudflare and the check rejects everything.
The dashboard snippet calls adslabShowInterstitial() and adslabShowRewarded(). Neither exists. The real ones are showint_adslab() and showrew_adslab().
Set the network's user percentage to 100 and split in your own code, or let them split and accept that your postbacks no longer show you the margin.
session-info answers pending for any token, including invented ones, so only the solved check means anything.
Offers are priced per country and void on proxies, so the country you send and the proxy check you run decide whether your conversions survive.
The $400 offer is an 18-step ladder paying per step, with almost all of it behind repeated real-money purchases. Designing your economy around it means designing for an event that never fires.