From 14b2bf7993752ca270d3440145f8d75fecb48145 Mon Sep 17 00:00:00 2001 From: Tamas Erdelyi Date: Mon, 12 Oct 2026 16:55:35 +0100 Subject: [PATCH] docs(app-api): say some endpoints are rate limited --- .../docs/API solutions/App API/patchstack-integration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/API solutions/App API/patchstack-integration.md b/src/content/docs/API solutions/App API/patchstack-integration.md index 22a2757..96f93b6 100644 --- a/src/content/docs/API solutions/App API/patchstack-integration.md +++ b/src/content/docs/API solutions/App API/patchstack-integration.md @@ -48,8 +48,8 @@ All Patchstack API endpoints return standard HTTP status codes. Your integration - **Sites per request** — `POST /site/add` and `POST /site/exists` accept between 1 and **100 URLs** per call in the `urls` array. Split larger batches across multiple requests. - **Listing sites** — `POST /sites/list` is paginated (`page`, `per_page`, default 20 per page); page through it when rendering large accounts. `POST /sites/list/basic` is *not* paginated — it returns the full `[{id, url}, …]` array for the account in one response, which is what makes it convenient for reconciliation. -:::note[No per-key request-rate limit] -The App API does not currently enforce a per-key request-rate limit on authenticated calls. Even so, when provisioning at large scale, batch your requests considerately rather than issuing one call per site — for example, pass multiple URLs in the `urls` array on `/site/add` (and `/site/exists`) instead of looping a separate request per site. +:::note[Rate limits] +Some App API endpoints are rate limited. If you receive `429 Too Many Requests`, wait a minute and retry. When provisioning at large scale, batch your requests considerately — for example, pass multiple URLs in the `urls` array on `/site/add` (and `/site/exists`) instead of looping a separate request per site. ::: ## Flow of integration & plugin