Getting Started with Wildfire API's and JSON feeds

wildfire api & json feeds allow partners to access wildfire's data rich affiliate network coupons and cashback opportunities, for partners building their own offer walls, extensions, marketing efforts, and more ensure you read through the essential information regarding our api & json structures docid\ bbiwqh1xlmejk6klsnmka docid\ kfgi2mirk7rikymt72ljp docid\ bghgjznc6erqn u55ducj docid\ ja2byx6fk44e3vc7rekjm how to handle multiple countries docid 8tndoxmq4z4afjxrfa0ln how to build links and tracking codes for cashback docid\ joexxcudngxrac8q7afji docid\ pl3 phzaubmp4kwtmqukx feel free to reference this checklist preparation & setup logic if paying out users, install the postman collection use the pre built collection with the included pre request script to automatically generate the required hmac authentication headers for api testing ingest sample data if live traffic is not yet active, ingest the public commission sample data (where applicationid is 0) to validate your dashboard’s ability to parse and display status changes coupon data feed logic because the coupon data feed provides raw data, the following logic must be implemented in the partner application coupon data feed normalize descriptions if the code field is null, parse the description field to extract coupon code patterns coupon data feed manual country filtering the feed is not pre filtered by region partners must filter coupons using the provided country codes to match the user's location coupons data feed date validity management suppress expired promotions handle "coming soon" promotions (future start dates) interpret "year 3000" end dates as "no expiration " coupons data feed language handling filter or translate coupons if the merchant passes codes in a language not supported by your ui (e g , us merchants passing spanish coupons) merchant & rate logic feed identify rate types percentage vs flat if a rate is flat, check the currency field (e g , usd, cad, eur) cache refresh rate implement a scheduled task to refresh the merchant data feed at least once every 24 hours optional refresh coupon data feeds every 6 hours to capture short lived offers disclaimer logic your ui must display "up to \[x]%" and include disclaimers that rates are subject to change link construction device id generation your system must call post /device to generate a device id for each unique user context before constructing links if doing cashback user attribution (tc parameter) to attribute a sale to a specific user in your system, you must append \&tc=\[your user uuid] to the tracking link wildfire will return this value in the commission report deep linking when linking to a specific product page, you must url encode the target url and append it as the last parameter (\&url= ) to prevent truncation by browsers multi country overide if your application serves users in multiple countries but uses a single app id, you must detect the user's location and append \&pc=\[countrycode] (e g , \&pc=ca) to tracking links to force the correct merchant program compliance logic accommodate stand down logic regularly ingest the stand down policy json feed this contains a list of domains and url parameters (e g , afsrc=1) that indicate a user is already affiliated with another publisher accommodate session suppression if a user visits a url matching the stand down list, your application (extension) must suppress all activation prompts for the duration of the user's session (typically 1 hour) commission reporting & payout logic signature verification when receiving a callback (webhook), calculate the sha 256 hmac of the request body using your callback key, then compare it to the x wf signature header to verify authenticity de duplication callbacks fire on every status change your system must upsert (update or insert) records by commissionid to avoid creating duplicate entries for the same transaction reconciliation (failsafe) callbacks are "fire and forget" (no retries) you must implement a nightly batch job that uses the commission api to fetch records modified in the last 24 hours and ensure any missed webhooks are captured status management do not release funds to users while the status is pending or confirmed wait for the status to change to paid (or ready if you assume the risk) before crediting user wallets split handling (v4 api) they need to handle the split payout and offer presentation you will see two splitpart values application (your share) and device (the user's share)