The Offerwall Dynamic API: Server-Driven Monetization Guide
The Offerwall Dynamic API: Server-Driven Monetization
The Perkox Dynamic API enables server-driven offerwall control: configure and serve offerwall content through the API without SDK redeploys. This guide covers the use cases.
What the Dynamic API Does
Fetch offerwall configuration and offers dynamically – update reward rates, offer lists, and design elements without shipping app updates.
Use Cases
Remote config for reward sizing, geo-specific offer lists, event-driven campaigns, and design refresh without store reviews.
Integration
Combine the Dynamic API with native SDKs: SDK for rendering, API for server-driven configuration. See the Perkox docs for endpoint details.
How the Dynamic API Works in Practice
The Dynamic API exposes endpoints for offerwall configuration, offer filtering, and reward rate management. A typical flow works like this: your backend calls the API to fetch the current offerwall configuration for a given user, including available offers, reward amounts, and display settings. The SDK receives this configuration and renders the offerwall accordingly. When you want to change reward rates – say, doubling coins during a weekend event – you update the configuration server-side. Every user who opens the offerwall after the change sees the new rates immediately. No app update, no store review, no waiting.
Consider a publisher running a holiday campaign. Without the Dynamic API, they would need to ship an app update with new offerwall settings, wait for store review, and hope users update within the campaign window. With the Dynamic API, they toggle a configuration flag server-side and every active user sees the holiday-themed offerwall on their next session. The campaign launches in minutes, not weeks.
Geo-Specific Offer Lists
One of the most powerful Dynamic API features is geo-targeting. Different markets have different offer availability, payout rates, and user preferences. The API lets you serve distinct offer lists per country without maintaining separate app builds. A user in Brazil sees survey offers optimized for Latin American panels; a user in Japan sees CPI campaigns from local app developers. Server-side filtering handles the logic; the SDK renders whatever the API returns.
Why This Matters
App store review cycles are the bottleneck for every monetization change. Apple’s review process can take 24-48 hours; Google’s can take hours to days. During that window, monetization opportunities pass. A flash sale offer, a seasonal campaign, a response to a competitor’s promotion – all blocked by review latency. The Dynamic API removes this bottleneck entirely. Configuration changes propagate instantly to every active user, giving publishers the agility to react to market conditions in real time.
This matters especially for live-ops teams running time-sensitive promotions. The ability to adjust reward rates, swap offer lists, or launch event campaigns without engineering involvement transforms monetization from a release-cycle activity into a daily optimization lever.
Key Takeaway
The Dynamic API brings server-driven control to offerwall monetization. By decoupling configuration from the app binary, publishers can update reward rates, offer lists, and design elements instantly – no SDK redeploy, no store review. Combined with native SDKs for rendering, it gives live-ops teams the agility to optimize monetization in real time while maintaining full control over the user experience.
Frequently Asked Questions
Why use the Dynamic API?
Change monetization config without app updates.
Does it replace SDKs?
No – it complements them with server-driven control.
Where is the documentation?
docs.perkox.com – Dynamic API section.
Start Monetizing with Perkox
Register as a Perkox publisher and integrate the rewarded monetization SDK. Read the documentation
Perkox provides rewarded monetization infrastructure – SDKs, tracking, analytics, and reward validation – for mobile apps and games across Android, iOS, Unity, Flutter, and React Native.