From 30cdd18db59406e2a925019227de96d4f0e75b55 Mon Sep 17 00:00:00 2001 From: Wen Bo Xie Date: Wed, 24 Jun 2026 18:59:57 +0800 Subject: [PATCH] fix: add migrations endpoint duration is 5 minutes (#43350) --- apps/docs/content/_partials/api_rate_limits.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/apps/docs/content/_partials/api_rate_limits.mdx b/apps/docs/content/_partials/api_rate_limits.mdx index e72382fd1c6..c050a467f80 100644 --- a/apps/docs/content/_partials/api_rate_limits.mdx +++ b/apps/docs/content/_partials/api_rate_limits.mdx @@ -57,6 +57,12 @@ Some endpoints have stricter rate limits than the standard 120 requests per minu **Note:** The `GET /v1/projects/:ref/database/context` endpoint has dual rate limiting. You can make up to 10 requests per minute, but also no more than 1 request per second to prevent burst traffic. +Some endpoints have the standard 120 requests per minute but with different timeout durations: + +| Endpoint | Limit | Duration | Reason | +| -------------------------------------------- | ------------ | --------- | ---------------------------------------------------- | +| `POST /v1/projects/:ref/database/migrations` | 120 requests | 3 minutes | Database migrations may require more processing time | + ### Best practices - **Monitor rate limit headers** - Check the `X-RateLimit-Remaining` header to see how many requests you have left. When it approaches 0, slow down your requests to avoid hitting the limit.