GoKart - Documentation - Offer Wall Integration
Integration Options
API Rate Limits
To ensure consistent platform performance and protect against misuse, GoKart enforces rate limits on key Offer Wall API endpoints. These limits are enforced at the IP level.
Why This Matters
If you're calling our APIs from server-hosted applications (rather than directly from client devices), all requests may originate from a single IP address or a small IP pool. This makes it more likely to hit the IP-based rate limits compared to distributed client-side integrations (e.g., from mobile apps). Be sure to architect your usage accordingly.
Rate Limits by Endpoint
Endpoint
Method
Description
Limit
Notes
/api/v1/offer-wall/offers
GET
Retrieves all active offers for display on an offer wall.
250 requests/min/IP
Returns a large payload and is called frequently. Rate limited to prevent abuse while supporting legitimate traffic.
/api/v1/offer-wall/offer-details
GET
Fetches detailed information for a specific offer.
60 requests/min/IP
Most details are available via /offers. This endpoint logs view events, so use it when users view specific offers.
/api/v1/offer-wall/offer-link
GET
Retrieves the tracking link for a clicked offer. Requires viewId.
60 requests/min/IP
Used when a user clicks into an offer. Logs a click event in our system.
/api/v1/offer-wall/offer-link-redirect
GET
Redirects the user directly to the offer tracking URL. Requires viewId.
60 requests/min/IP
Similar to /offer-link, but includes the redirect. Logs a click event. Not suitable for bulk use.
/api/v1/offer-wall/pub-member/offers
GET
Retrieves offer status (in-progress, completed) for a user.
250 requests/min/IP
Typically called alongside /offers to show real-time offer state. Supports high-volume use cases but still rate limited to protect system performance.
There are no rows in this table
Best Practices
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.