Use the API when you want to render your own UI, inspect click context or connect server-side reward events. Examples use placeholders for site identity, users and signatures.
Requests are scoped to a publisher site. Use the site key for public placement requests and the site secret for HMAC verification on server-side callbacks.
| Value | Where it is used |
|---|---|
site_key | Public identifier used by iFrame, Web SDK, Android SDK and Offers API. |
site_secret | Private value used to verify HMAC-signed postback payloads. |
user_id | Publisher-side user identifier passed through the reward flow. |
Returns offer data for the supplied site and user context.
GET https://pro.adswedmedia.com/api/offers?site_key={site_key} &user_id={user_id} &format=offerwall
| Parameter | Description |
|---|---|
site_key | Publisher site key. |
user_id | Publisher user id. |
format | Placement format such as offerwall, banners, surveys or PTC. |
Looks up click context for investigation and postback recovery workflows.
GET https://pro.adswedmedia.com/api/click-lookup?site_key={site_key} &click_id={click_id}
Credit, reject and chargeback events use the same callback shape. Verify the signature before applying the event.
event=credit|reject|chargeback
site_key={site_key}
user_id={user_id}
click_id={click_id}
reward={reward_amount}
signature={hmac_sha256}
Site identity or signature could not be verified.
The requested click, offer or resource could not be found.
Required parameters are missing or not accepted.
The client should slow down and retry later.