From d37cda77dcdf7335aa7f80d085d8fdee3b6258e3 Mon Sep 17 00:00:00 2001 From: Will Strinz Date: Thu, 22 Oct 2026 12:48:03 -0500 Subject: [PATCH 1/2] Document the workflow details rate limit Co-Authored-By: Claude Opus 5.5 --- source/includes/rest/_workflows.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/source/includes/rest/_workflows.md b/source/includes/rest/_workflows.md index f2beb878d46..a83d369d747 100644 --- a/source/includes/rest/_workflows.md +++ b/source/includes/rest/_workflows.md @@ -575,6 +575,23 @@ The `ETag` describes this view of the workflow rather than the workflow's stored is a cache validator only. Two workflows that differ solely in fields this endpoint withholds share an `ETag`, and a change confined to a withheld field does not invalidate one. +### Rate limits + +> If the account has made more than 2,000 requests in the hour, responds with a 429 Too Many Requests and a Retry-After header: + +```json +{ + "errors": [{ + "code": "rate_limit_exceeded", + "message": "Rate limit exceeded: at most 2000 requests per account per hour." + }] +} +``` + +This endpoint is limited to 2,000 requests per account per hour, on top of the +[general rate limit](#rate-limiting). Past that it responds with a `429 Too Many Requests`, and +`Retry-After` gives the number of seconds to wait. + ### HTTP Endpoint `GET /v2/:account_id/workflows/:workflow_id/details` From bec7e732b1aa0cfbf9323930aa338298aaf1c2af Mon Sep 17 00:00:00 2001 From: Will Strinz Date: Thu, 22 Oct 2026 14:16:53 -0500 Subject: [PATCH 2/2] Tighten the workflow details rate limit wording Co-Authored-By: Claude Opus 5.5 --- source/includes/rest/_workflows.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/includes/rest/_workflows.md b/source/includes/rest/_workflows.md index a83d369d747..68367162863 100644 --- a/source/includes/rest/_workflows.md +++ b/source/includes/rest/_workflows.md @@ -577,7 +577,8 @@ an `ETag`, and a change confined to a withheld field does not invalidate one. ### Rate limits -> If the account has made more than 2,000 requests in the hour, responds with a 429 Too Many Requests and a Retry-After header: +> If the rate limit is exceeded, responds with a 429 Too Many Requests and a +> Retry-After header indicating when the limit resets: ```json { @@ -588,9 +589,8 @@ an `ETag`, and a change confined to a withheld field does not invalidate one. } ``` -This endpoint is limited to 2,000 requests per account per hour, on top of the -[general rate limit](#rate-limiting). Past that it responds with a `429 Too Many Requests`, and -`Retry-After` gives the number of seconds to wait. +This endpoint has its own rate limit of 2,000 requests per account per hour, in addition to the +[general rate limit](#rate-limiting). ### HTTP Endpoint