Meta tags:
description=Overview 📘 Heads up: We introduced rate limits on 4 June 2025. Please review this document to ensure your integration isn’t affected. Rate limits are essential safeguards that ensure fair and stable API access for all clients. By implementing these limits, we help to prevent service disruptions cau…;

Headings (most frequently used words):

rate, requests, limits, limit, get, per, minute, overview, response, best, practices, for, management, faq, heads, up, request, classification, tracking, endpoints, and, read, 600, non, write, 60,

Text of the page (most frequently used words):
rate (18), the (17), for (16), api (15), #limits (12), limit (11), requests (9), and (8), endpoints (7), data (6), request (5), are (5), all (5), get (5), per (5), tracking (4), minute (4), your (4), response (3), classification (3), they (3), our (3), analytics (3), these (3), used (3), header (3), retry (3), after (3), implement (3), http (3), with (3), post (3), records (3), 600 (3), each (3), endpoint (3), group (3), this (3), ensure (3), web (3), faq (2), best (2), practices (2), management (2), overview (2), updated (2), months (2), ago (2), platform (2), handle (2), not (2), fetching (2), seconds (2), you (2), verb (2), that (2), complex (2), queries (2), non (2), even (2), only (2), retrieving (2), new (2), uses (2), quota (2), rather (2), than (2), instance (2), approach (2), apps (2), path (2), jump (2), changelog (2), docs (2), home (2), log (2), core, designed, high, volumes, traffic, sending, such, pageviews, events, limited, respect, values, exponential, backoff, retries, gracefully, reduce, repetitive, calls, store, frequently, accessed, locally, caching, efficient, strategies, avoid, unnecessary, polling, optimize, patterns, indicates, number, wait, before, making, another, status, code, 429, too, many, when, exceed, will, respond, note, strictly, based, purpose, operation, why, count, against, using, method, retrieve, removing, delete, updating, existing, patch, put, creating, write, exclusively, user, lists, getting, app, details, read, current, defined, follows, limiting, implementation, leaky, bucket, algorithm, means, gradually, replenished, throughout, time, window, resetting, once, operations, receive, approximately, second, being, refreshed, start, exceeding, won, affect, maintains, its, own, granular, allows, more, flexible, usage, while, still, protecting, individual, from, overload, cdp, apply, address, client, separate, pools, determined, prefix, example, essential, safeguards, fair, stable, access, clients, implementing, help, prevent, service, disruptions, caused, excessive, consistent, performance, across, helps, protect, infrastructure, experience, introduced, june, 2025, please, review, document, integration, isn, affected, heads, copy, page, content, agents, visit, https, developers, piwik, pro, llms, txt, index, pages, formatted, markdown, openapi,

Text of the page (random words):
rate limits for ai agents visit https developers piwik pro llms txt for an index of all pages formatted in markdown and endpoints in openapi jump to content home docs web api changelog log in web api log in home docs web api changelog rate limits jump to rate limits copy page overview heads up we introduced rate limits on 4 june 2025 please review this document to ensure your integration isn t affected rate limits are essential safeguards that ensure fair and stable api access for all clients by implementing these limits we help to prevent service disruptions caused by excessive requests and ensure consistent performance across our platform this approach helps protect our infrastructure and your experience with the api request classification these limits apply per ip address for a client instance with separate rate limit pools for each api endpoint path group an endpoint path group is determined by the api prefix for example api apps api analytics api cdp exceeding the limit for api analytics endpoints won t affect your rate limit quota for api apps each endpoint group maintains its own limits this granular approach allows for more flexible api usage while still protecting individual endpoints from overload the rate limiting implementation uses a leaky bucket algorithm it means the request quota is gradually replenished throughout the rate limit time window rather than resetting all at once for instance if your limit is 600 requests per minute for get operations you ll receive approximately 10 new requests per second rather than all 600 being refreshed at the start of each minute current limits are defined as follows get read requests 600 requests per minute retrieving data e g fetching user lists getting app details uses http get verb exclusively non get write requests 60 requests per minute post creating new records put patch updating existing records delete removing records complex queries using post method even if they only retrieve data note classification is strictly based on the http verb used not on the purpose of the operation that s why post requests used for complex queries count against the non get limit even if they re only retrieving data rate limit response when you exceed the rate limit the api will respond with http status code 429 too many requests response header x retry after seconds the x retry after header indicates the number of seconds to wait before making another request best practices for rate limit management optimize request patterns avoid unnecessary polling implement efficient data fetching strategies implement caching store frequently accessed data locally reduce repetitive api calls handle rate limits gracefully implement exponential backoff for retries respect the x retry after header values faq tracking endpoints and rate limits tracking endpoints are not rate limited they are the core of our analytics platform and designed to handle high volumes of traffic these endpoints are used for sending all tracking data such as pageviews events and so on updated 10 months ago updated 10 months ago overview request classification rate limit response best practices for rate limit management faq tracking endpoints and rate limits