API
The API provides publishers with access to a list of available offers tailored to their app.
Last updated
Was this helpful?
The API provides publishers with access to a list of available offers tailored to their app.
Last updated
Was this helpful?
By integrating this API, publishers can seamlessly fetch and display these offers within their own user interface. This allows for the creation of fully native and personalised in-app experiences that align with the app’s design and user flow, enhancing user engagement and improving conversion rates.
Pre-approval from PubScale team is required for the offerwall integration. Please contact your account manager or reach out to support before starting this integration.
In order to access offers API. Following Keys need to be generated.
Pub Key (Generated once per publisher)
App ID
In order to generate an App ID follow this guide for instructions on . Once completed, you will receive a unique 8-digit App ID. This will be used as App ID to access the API.
In order the generate a Publisher Key a pre-approval is required. This is a one time approval for a publisher. Please contact account manager for the same.
After your account is approved, you can proceed with the following steps to generate your Publisher API Key.
When you regenerate the Offerwall API Key, the new key will apply to all apps linked to your account.
Once logged in, you’ll find Settings in the side navigation panel.
Go to the API Key section to generate your Offerwall API key. If you don't see this section, please contact your account manager for enabling access.
Navigate to the Offerwall API section to access and create your Offerwall API key.
Please copy the key from the image and paste it into your Offerwall API setup.
The API provides a list of offers available for your app, which can be used to display and run offers on your platform.
Offers are cached on our server and refreshed every 5 minutes. We recommend updating your inventory accordingly.
The keys generated in the previous steps must be included in the following headers when making API requests.
These are Mandatory for accessing the API.
App-Id – The unique App ID generated for your app during the setup process.
Pub-Key – The unique key generated for your publisher account during setup. This key is shared across all apps within the same account.
page
Integer
The page
field in the Offers API response indicates the current page number and should always be a positive integer.
size
Integer
The size
field in the Offers API response represents the number of offers returned in that response and should always be a positive integer.
filt
Array
Contains an array of filters to be applied to the Offers API request to refine the results based on specified criteria.
dim
String
Specifies the dimension on which the filter is applied. Supported values are offer_type
, platform
, and country
.
match
Model
Contains details about the filter to be applied, including the values to filter by and the match type used for filtering.
type
String
Specifies the match type to be used for the filter. Supported values are any
(matches any of the provided values) and exact
(requires a single, exact value match).
values
Array
Contains the values to apply the filter on. Allowed values depend on the specified filter dimension.
You can use the tracking link provided in the trk_url
field of each offer in the API response to start sending click events to Pubscale. This tracking link is essential for monitoring user interactions and attributing tasks correctly.
Purpose
The trk_url
is used to track clicks from users on a particular offer. When a user interacts with an offer, your app or system should trigger this URL with the appropriate parameters.
The following query parameters are supported for integration with the tracking URL:
user_id
The unique identifier of the user who clicks on the offer. This will be included in the callback. Special characters aren't allowed except "_","@","-" and ".".
gaid
Google Advertising ID (required for Android users).
idfa
Identifier for Advertisers (required for iOS users).
c1-c5
Custom parameters can be appended to the tracking URL by the publisher and will be included in the callback for reference. Special characters aren't allowed except "_","@","-" and "."
This step is manadatory for rewarding users.
Set up the Server-to-Server (S2S) callbacks to receive instant updates whenever a user completes an offer and earns a reward. When an offer is completed, our server will send a notification to the configured callback URL. This callback provides the necessary information to process and verify the reward for the user in your application.