Skip to content

API Changelog


May 9, 2022 – Multi-Reward for Static API

  • Added is_multi_reward field to the Static API results for determining if a campaign is single reward or multi reward.
  • Added reward_type parameter to the Static API call for retrieving multi-reward campaigns.
  • Added all_goals_completed macro to Postbacks to inform publishers if the player has completed all the goals on a campaign.

October 2, 2020 – Postbacks v2 released

  • Postback fields moved from Offerwall page to Edit App page
  • Added “Postback Key” field to postback settings. This is used in Postback Hashing, a security feature we’ve introduced in v2 to help publishers verify the authenticity of postbacks they receive.

June 17, 2020 – Offer Wall API endpoint updated

  • Updated endpoint to use ‘/json’ instead of ‘&json’

October 1, 2019 – New parameter added

  • Added the new “limit” parameter to limit the amount of offers returned to a set number

Jan 25, 2019 – New offer object field added

  • Introduced new fields in the Offer Wall API response within the offer object “render_sticker”, “offer_sticker_text_1”, “offer_sticker_text_2”, “offer_sticker_text_3”, “offer_sticker_color_1” “offer_sticker_color_2”, “offer_sticker_color_3”

Jan 24, 2019 – New offer object field added

  • Introduced new field in the Offer Wall API response within the offer object “short_description”

Jan 14, 2019 – New category value added

  • For the Offer Wall API and the Static API, we’ve added an additional offer category value called user_info_request. If an offer has user_info_request as one of it’s categories, this means that in order for the offer to convert, the end user will be required to supply information to the advertiser such as their email address, gender, age etc.

Dec 19, 2018 – Static API Documentation updated

  • Corrected the accepted values for platform and categories. The platform parameter accepts the value “all” whereas the categories parameter does not.

Dec 3, 2018 – Version 1

  • Change API URL to require the parameter playerid replacing the previous parameter userid. The userid parameter is still supported but will be deprecated in future versions.
  • Added support for publishers to use player_id in postbacks replacing the previous user_id macro. The user_id macro is still supported but will be deprecated in future versions.

Updated on May 9, 2022

Back to top