Create an offerwall app

An offerwall is a hosted, brandable list of offers for your app or site. Your users complete offers, you credit them in your own currency (coins, gems, points), and you keep the difference.

1. Create the app placement

Go to Tools → Apps and create a new app. An app placement is the unit everything else hangs off: it owns the App ID, the API key, the currency name and the exchange rate.

Three fields are worth thinking about before you save:

• Currency name and rate. The rate converts an offer's payout into your currency. It is applied server-side, so the points value in the feed is already your number.
• Offer filters. Anything you exclude here never reaches the wall.
• Postback URL. Where we notify your server that a conversion completed.

2. Wait for approval

A new placement starts pending. Until it is approved, API calls answer with App Pending, and after a rejection with App Rejected. You can see the state on the app's page.

Approval is about the traffic source, so it helps to have the site or app live and reachable before you apply.

3. Embed the wall

There is nothing to sign and nothing to compute. The only URL you need is the one printed on your app's page:

<iframe
  src="https://titan.toroads.com/123/end-user-42"
  style="border:0;width:100%;height:720px"
  title="Offers"></iframe>

Replace 123 with your App ID and end-user-42 with your own identifier for the signed-in user. You can also just link to that URL instead of framing it.

Your api_secret is not involved here. It is used only to verify the postbacks we send you, which is the next step.

4. Receive the postback

When a user completes an offer, we call your postback URL. That call is what tells you to credit them. Verify it with your api_secret before you award anything: an unverified postback endpoint is an open faucet.

Credit the user against the user_id you put in the iframe URL. That is the only thing tying a conversion back to a person in your system, which is why it must be your stable identifier and not something that changes between sessions.

5. Optional: build your own wall

If the hosted wall does not fit your app, you can render offers yourself from the offer feed and keep only the tracking links:

curl -H "Authorization: Bearer APP_API_KEY" \
  "https://api.toroads.com/v2/offers/123/end-user-42?country_code=US&platform=android"

Each offer comes back with a url that is already a tracking link. Send the user there and the click is recorded for you. Do not build that URL by hand; it is an encrypted token.

The full parameter list and response shape are in the developer documentation.

v2 takes an Offerwall App ID. Handing it a Content Locker app id is refused with Wrong App ID. The two feeds are not interchangeable.

Next

• Verify your identity, which is what makes a balance payable.