Publisher offers API
Offers V2 has three different authentication contexts. Choose the endpoint family that matches your slot; the credentials are not interchangeable.
| Interface | Base path | Authentication | Purpose |
|---|---|---|---|
| Publisher console | /publisher/v2 | Dashboard session bearer token with publisher role | Create placements and slots, manage callbacks, view reports |
| User-bound SDK | /sdk/v2 | Short-lived session bearer token | Fetch personalized offers, launch, check reward status |
| Static offer feed | /publisher/v2/ad-slots/{adSlotId}/static-offers | X-RapidoReach-Static-Key | Poll non-personalized inventory from your server |
The foundation routes require Offers V2 publisher enablement. Offer delivery routes also require the offer delivery capability; a disabled route can return 404 not_found. A verified placement and ready slot are additional checks. The console routes use a logged-in dashboard session and are documented for integration context; they are not a replacement for a dedicated partner API credential.
Integration sequence
The route-checked endpoint index lists every publisher Offers V2 console, static-feed, and user-bound SDK method and links to its reference. It excludes the administrator review and separate rewarded-video APIs.
- Create a placement and slot in the console.
- Configure callback security and request placement review.
- For an Offerwall or Offer API slot, issue a user session and fetch offers. For a Static API slot, issue a slot key and poll the feed.
- Verify confirmed rewards from the signed callback, then monitor deliveries and reports.
All amounts ending in Micros are integer millionths of a USD unit unless a field says otherwise. IDs are opaque. Store secrets server-side, use HTTPS in production, and make reward writes idempotent.