Asknicely Rate Limits
AskNicely enforces two rolling windows (10 seconds and 60 seconds) per account, reported live on every response through RateLimit-Req10s-* and RateLimit-Req60s-* headers. A separate, lower pair of limits applies to /contact/trigger; AskNicely's own guidance is to use the bulk /contacts/add endpoint instead of hitting that limit. Exceeding a window returns HTTP 429 with a JSON body naming the window, the count and the limit, plus a Retry-After header.
Asknicely Rate Limits is the machine-readable rate-limit profile for AskNicely on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions, measuring requests_per_10_seconds and requests_per_60_seconds.
Limit state is signalled in the limit10s, remaining10s, limit60s, and remaining60s response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled.
Tagged areas include Rate Limiting, Customer Experience, and Surveys.
limit10sremaining10slimit60sremaining60s
Limits
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.