Pollfish · Rate Limits

Pollfish Rate Limits

Pollfish does not publish fixed numeric per-minute rate limits for its public REST APIs. The Dashboard API (app management and analytics) is authenticated with HTTP Basic Auth and documents functional constraints rather than throttle ceilings - most notably that analytics queries (performance, revenue, performanceByCountry) must span a from/to window of no more than 31 days per request. The survey-serving / offerwall API on wss.pollfish.com is governed by survey supply and eligibility rather than a request quota: a register call returns HTTP 204 when no survey matches the respondent, the HTML offerwall is capped at 60 surveys while the JSON offerwall returns a longer list, and each respondent can complete a given survey only once (enforced via tx_id and duplicate termination). Server-to-server postback callbacks are fired by Pollfish, so their volume tracks survey completions rather than a client limit.

Pollfish Rate Limits is the machine-readable rate-limit profile for Pollfish on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring requests, days, surveys, and completions.

The profile also includes 4 backoff/retry policies defined and response codes documented for noContent and badRequest.

Tagged areas include Surveys, Monetization, Rate Limiting, and Quotas.

5 Limits
SurveysMonetizationRate LimitingQuotas

Limits

Dashboard API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the Dashboard API.
Analytics Date Window request
days
31
The from/to window on performance, revenue, and per-country endpoints must not exceed 31 days.
HTML Offerwall Surveys request
surveys
60
The HTML offerwall returns up to 60 surveys; the JSON offerwall (content_type=json) returns a longer list.
Survey Completions Per Respondent respondent
completions
1 per survey
Each device_id may complete a given survey only once; repeats are rejected as duplicates (tx_id enforced).
Survey Availability respondent
surveys
eligibility-bound
Register returns HTTP 204 when no eligible survey exists for the respondent; supply is not a fixed quota.

Policies

No Content Signaling
The register/offerwall call returns HTTP 204 (no body) when no survey is available rather than an error; use HEAD to check availability cheaply.
Duplicate Prevention
A user may complete a specific survey only once; duplicate attempts are terminated and reported via the users_log disqualification reasons and s2s term_reason.
Reward Signing
When passing reward_conversion, callers must supply a valid HMAC-SHA1 sig; failed validation returns 400 "Hash check failed".
Backoff Strategy
Clients should implement retries with exponential backoff and honor the 31-day analytics window to avoid rejected queries.

Sources