Integration docs
All Offers API
Overview
The Offers API provides publishers with access to available advertising campaigns (offers) tailored to their account status, target device, and promotion methods. Each offer includes comprehensive details about payouts, requirements, targeting restrictions, and multi-tier reward structures.
Quick Start
Get your first offers in 30 seconds:
Authentication
All requests require your API key. Include it in the key parameter of every request.
Important
Keep your API key secure - never expose it in client-side code or public repositories.
To find your API Key, log into your Publisher Account, go to My Account -> API Key
Base URL
https://publishers.revenueuniverse.com/affiliates/api.php
Request Parameters
Parameter | Type | Required | Description |
|---|---|---|---|
| integer | ✅ | Your offer wall ID |
| string | ✅ | Your API authentication key |
| string | ✅ | Must be set to |
| integer | ✅ | Use |
| integer | ❌ | Get a specific offer by campaign ID |
Response Format
Success Response
Error Response
Offer Object Reference
Basic Properties
Field | Type | Description |
|---|---|---|
| integer | Unique campaign identifier |
| string | Campaign name |
| string | Offer headline (short description) |
| string | Detailed offer description |
| string | What users need to do to earn rewards |
| string | Additional terms and conditions |
| string | Offer category (e.g., "Mobile Apps", "Purchase") |
| integer | Type of product promoted in offer, see mapping below |
Offer Type Mapping
ID | Category |
|---|---|
0 | Undefined |
1 | Casino/Gambling |
2 | Loyalty Offers |
3 | Non Branded Submits |
4 | Games |
5 | Trial/Purchase |
6 | Surveys |
7 | Branded |
8 | Mobile - Non Gaming |
9 | Alcohol/Tobacco/Drugs |
10 | Other Mature |
11 | Social Casinos |
Financial & Performance Information
Field | Type | Description |
|---|---|---|
| float | Your payout in USD |
| integer | Virtual currency awarded to users |
| float | Historical earnings per click (network-wide, last 7 days) |
| float | Historical conversion rate (network-wide, last 7 days) |
Targeting & Restrictions
Field | Type | Description |
|---|---|---|
| string | Target platform: |
| array | Allowed country codes (ISO 2-letter) |
| array | Allowed states/provinces ( |
| integer | Minimum user level required (0 = no restriction, do not serve offers > 0 without confirmation of eligibility from User-Level API) |
| integer | Minimum OS version (null = no restriction) |
Capping & Reporting Time
Field | Type | Description |
|---|---|---|
| object | Budget restrictions |
| string | Cap period: |
| string | Maximum conversions allowed |
| string | Current usage count |
| string | Expected tracking delay: |
Image Assets
Field | Type | Description |
|---|---|---|
| array | Available images/banners |
| integer | Image width in pixels |
| integer | Image height in pixels |
| string | Direct image URL |
URLs
Field | Type | Description |
|---|---|---|
| string | Click tracking URL (append UID after sid2= before use) |
| string | Landing page preview without tracking |
| string | App Store ID or Android package name |
Multi-Reward Offers (Tiers)
Versions 2 and above support offers with multiple reward tiers. These appear when tiers: true:
Tier Properties
Field | Type | Description |
|---|---|---|
| string | What the user must complete for this tier |
| integer | Virtual currency for this specific tier |
| float | Your payout for this tier in USD |
| string | Tier identifier for tracking (can be empty) |
Working with Multi-Reward Offers
currency_with_tiers: Sum of all possible currency rewardssid4: Use this identifier in postback tracking by adding $sid4$ to your postback templateEmpty
sid4values are valid and represent completion events
Multi-Reward Event Tracking
User progression through Multi-Reward campaigns can be tracked by (1) using postbacks from RevU or (2) by calling the User Level Offer API.
Use Cases:
Progress Visualization: Display completion indicators for partially completed multi-reward offers
Offer Filtering: Hide completed tiers while maintaining visibility of available progression opportunities
User Experience Optimization: Provide contextual information about user progress and remaining earning potential
Option 1: Implementing Tier-Specific Tracking with Postbacks
To enable precise tracking of multi-reward offer completions, incorporate the $sid4$ parameter into your postback URL template. This parameter will be dynamically populated with the tier-specific event identifier that corresponds to the sid4 value returned in the Offers API response.
Postback Template Example:
https://your-domain.com/postback?user_id=$uid$&campaign_id=$campaign$&tier=$sid4$&payout=$rate$
Event Identifier Specifications
Direct Correlation: The $sid4$ placeholder receives the exact sid4 value from the API response, enabling accurate attribution of tier-specific conversions within multi-reward campaigns.
Empty Value Handling: The sid4 parameter may contain an empty string, which constitutes a valid event identifier. Your postback processing logic must recognize empty sid4 values as legitimate tier completion events, not as data omissions or system errors.
Uniqueness Constraints: The sid4 value maintains uniqueness only within the scope of its associated campaign. To ensure system-wide uniqueness, combine the sid4 value with the $campaign$ identifier in your tracking implementation to prevent identifier conflicts across different campaigns.
Single-Reward Offer Considerations
Standard offers with tiers: false do not include sid4 values in their API response structure. However, when the $sid4$ placeholder is present in your postback template, the system may still populate this parameter for single-reward offers. In such scenarios:
Disregard the
sid4value for offers wheretiers: falseInterpret any postback as confirmation of complete offer fulfillment
Remove the completed offer from the user's available offer inventory
Option 2: User Level Offer API to Check Progression
The User Level Offer API provides comprehensive tracking capabilities for monitoring user progress across individual tiers within multi-reward offers. Implement API calls that include the user identifier (UID) to retrieve current completion status for all campaign tiers.
Implementation Process
API Call: Execute a request to the User Level Offer API with the required UID parameter, append User-IP and Device if called server-side
Response Processing: Locate the campaign-specific
tiers_urlendpoint within the API responseStatus Retrieval: Query the
tiers_urlto obtain real-time completion status for each available tier
The tiers_url endpoint delivers current progress data, enabling dynamic user interface updates and accurate offer presentation based on individual user advancement within multi-reward campaigns.
Additional Information & Usage Recommendations
Common Error Codes
Status | Message | Solution |
|---|---|---|
400 | "Invalid offer wall." | Check your wall ID parameter |
400 | "This API is incompatible with your affiliate account status." | Contact support to verify account status |
400 | "No eligible promo types found." | Specify a valid offer wall or check targeting settings |
500 | "Internal server error." | Retry request or contact support if persistent |
Example Requests
Get All Offers
Get Specific Offer
Filter by Platform
Integration Tips
Click URL Modification
The url field contains a template that needs modification before serving to users - append the userId after sid2= without modifying the rest of the URL:
Cap Management
Check the cap object to avoid showing exhausted offers:
Multi-Reward Tracking
For offers with tiers: true, implement progress tracking:
Rate Limiting
API calls are monitored for abuse
Recommended: Cache responses for 2-10 minutes
Excessive requests (>5 per minute) may result in temporary blocking
Support
For technical support or questions about specific offers, reach out to your account manager or sales contact.