Skip to main content
The Everflow API enforces rate limits to ensure platform stability. The quota is per customer — it is a single shared bucket across every API key, every user, and every surface (REST API and MCP) that authenticates under that network. There is no per-key or per-user allocation.
MCP and REST API requests draw from the same per-customer bucket. There is no separate quota for MCP — every tool call an AI agent makes counts against the same limit as your direct API calls. If you run an AI agent in parallel with automated API scripts, they compete for the same budget.

​
Request quotas

User typeRequests per second (per customer)
Network30
Affiliate5
Advertiser5
Partner5
Rate limits reset every 30 seconds. Every response includes headers indicating your current quota:
HeaderDescription
X-RateLimit-LimitTotal requests allowed per 30-second window
X-RateLimit-RemainingRequests still available in the current window
Once you exhaust your limit, all requests return a 429 Too Many Requests error until the window resets.

​
Concurrent request limits

The /v1/networks/reporting/* endpoints allow a maximum of 10 concurrent requests. Additional concurrent requests will return an error. Wait for in-flight requests to complete before sending new ones.

​
Granular report quotas

Reporting requests that include certain high-cardinality columns are served by a separate, more granular reporting backend and are subject to their own hourly quota:
User typeQueries per hour
Network1,000
Affiliate1,000
Advertiser1,000
The hourly limit is enforced on a rolling 60-minute window (not aligned to clock hours).
Affiliate and Advertiser granular report quotas are applied at the network level — the 1,000/hour limit is shared across all affiliates (or advertisers) of a given network, not allocated per individual entity.

​
Columns that trigger granular reporting

A reporting request falls under this quota when it includes at least one of these columns.
Geolocation: Country, Region, City, DMA, Carrier, ISP, Connection Type, Postal Code, Is ProxyDevice: Platform, OS Version, Device Type, Browser, Device Brand, Language, Device Model, Device MakeOffer: Offer Group, Offer URL, Event Name, Advertiser Event Name, Payout Type, Payout Amount, Revenue Type, Revenue Amount, Custom Payout RevenueMiscellaneous: Adv1–Adv5, Sub1–Sub5, Source ID, Project ID, Referrer, Coupon Code, Tracking Domain, Order ID, Attribution Method, Account Referred By, Error Code, Cookie Based, Click Tracking Method, Data Supplement