Offerwall integration guide
Everything you need to embed the RewardTym offerwall and wire the S2S postback that credits your users — the offerwall API, the postback URL, and the macros, in one place.
GET https://your-server.com
/rewardtym/postback/TOKEN
?uid={user_id}
&amount={payout_amount}
¤cy={currency_name}
&status={status}
&txn={conversion_id}
# credit only when status == approved
# dedupe on conversion_idEmbed the offerwall
Load your hosted offerwall URL in an iframe on the web or a webview in your app, passing your partner ID and a unique, stable user ID. There is no SDK to compile and no app-store review tied to the integration.
Use your own internal user ID (never an email or anything identifying), URL-encode it, and send the same value every time that user opens the wall so their rewards aren't split across IDs.
<!-- Web: iframe. In an app, load the same URL in a webview. --><iframe src="https://rewardtym.online/offerwall?partnerid=YOUR_PARTNER_ID&userid=USER_ID" width="100%" height="100%" style="border:0"></iframe>Set up your S2S postback URL
A postback (callback) URL is an endpoint on your server that RewardTym calls on every confirmed conversion. Server-to-server tracking is reliable and tamper-resistant — it does not depend on the user's browser or an SDK. You give RewardTym the URL once; it is called automatically from then on.
Build a single HTTPS endpoint with a long, unguessable path. It can accept a JSON POST, or a GET whose query string you define with macros. RewardTym substitutes each {macro} with the URL-encoded conversion value.
https://your-server.com/rewardtym/postback/RANDOM_TOKEN ?uid={user_id} &amount={payout_amount} ¤cy={currency_name} &status={status} &txn={conversion_id}Offerwall macros
Every field of a conversion is available as a macro you can drop into your postback URL. Place the ones you need; RewardTym fills them in on each call.
{user_id} your unique user ID (the one you passed in){conversion_id} unique transaction ID — use for idempotency{payout_amount} reward amount to credit, in your currency{currency_name} your reward currency (e.g. coins){status} approved | pending | rejected | reversed{lt_campaign_id} the offer/campaign ID{campaign_name} human-readable offer name (good for the note){country} {device} {ip} conversion metadataCredit the user safely
Credit a user only when status is approved, and treat conversion_id as idempotent. A conversion can arrive as pending, approved, rejected or reversed; only approved is payable, and because deliveries can retry, the same conversion_id may arrive more than once.
Gate the wallet credit on status == "approved", store each conversion_id you process, and reverse a credit if a later rejected or reversed event arrives for the same ID. This is the same verification that powers our offerwall fraud prevention. New to postbacks? Read what a postback URL is.
Offerwall integration & postbacks — your questions
Embedding, S2S postbacks, macros, and crediting users safely.
Embed your hosted offerwall URL in an iframe (web) or webview (app), passing your partner ID and a unique, stable user ID in the query string. When a user completes an offer, RewardTym fires a server-to-server postback to your callback URL so you can credit their balance. No SDK is required.
Ready to integrate?
Embed the offerwall, wire your postback, and start earning on confirmed conversions. We'll help you go live.