Introduction to Affike

Welcome to the Affike documentation. Here you will find all required information to integrate our offerwall into your website or app in just a few minutes.

Add your Placement

In order to integrate our Affike Offerwall, first you have to add your app/website placement. Once you have your placement approved, you will have an API KEY and a SECRET KEY that you will need to integrate our Offerwall.

Steps to add your placement

1. 1

   Login or Signup your account with Affike

   Sign UpLogin
2. 2

   Go to your Publisher Dashboard and click on "Placements"

3. 3

   Click "Create Placement" and fill up the form

4. 4

   Allow us up to 24 hours to check your placement request

   Within 24 hours, your account will be approved by our team. After that, make sure to add your postback and reward configs (Exchange Rate, Currency Name, etc.)

Website Integration

If you are looking to integrate the offerwall into your website, either open the offerwall in a new tab or show the offerwall in an iframe.

JavaScript Integration

Open the offerwall in a new browser tab:

window.open("https://affike.com/offerwall/[API_KEY]/[USER_ID]")

iFrame Integration

Embed the offerwall directly in your page:

<iframe 
  src="https://affike.com/offerwall/[API_KEY]/[USER_ID]"
  width="100%"
  height="600"
  frameborder="0"
  scrolling="yes">
</iframe>

https://affike.com/track/click?offer_id=OFFER_ID&click_id=YOUR_TRACKER_CLICK_ID

Optional Parameters

You can pass additional parameters to customize the offerwall experience:

https://affike.com/offerwall/[API_KEY]/[USER_ID]?subid=[SUBID]&country=[COUNTRY]

Postback Setup

Configure your server-to-server postback URL to receive conversion notifications and reward your users automatically.

Postback URL Format

We will send a GET request to your postback URL with the following parameters:

https://yoursite.com/postback?user_id={user_id}&click_id={publisher_click_id}&payout={payout}&offer_id={offer_id}&transaction_id={transaction_id}&signature={signature}

Available Macros

Response Codes

Your server should respond with one of the following:

• 200 OK - Conversion processed successfully
• 400 Bad Request - Invalid parameters
• 409 Conflict - Duplicate transaction

Security

Verify postback authenticity using the signature parameter to prevent fraud.

Signature Verification

The signature is generated using HMAC-SHA256 with your Secret Key:

// PHP Example
$secret_key = "YOUR_SECRET_KEY";
$string_to_sign = $user_id . $payout . $transaction_id;
$expected_signature = hash_hmac('sha256', $string_to_sign, $secret_key);

if ($signature === $expected_signature) {
    // Valid postback - process the conversion
} else {
    // Invalid signature - reject the request
}

// Node.js Example
const crypto = require('crypto');

const secretKey = "YOUR_SECRET_KEY";
const stringToSign = user_id + payout + transaction_id;
const expectedSignature = crypto
  .createHmac('sha256', secretKey)
  .update(stringToSign)
  .digest('hex');

if (signature === expectedSignature) {
  // Valid postback - process the conversion
} else {
  // Invalid signature - reject the request
}

Frequently Asked Questions