From 5db74171a8d4188c05b528c3f14e33ce215091b7 Mon Sep 17 00:00:00 2001 From: relay-docs-bot Date: Tue, 28 Jul 2026 12:53:07 +0000 Subject: [PATCH] docs(drift): draft from internal source Requested by @ipeleg via /publish-docs-pr --- references/api/api-keys.mdx | 3 +++ references/api/changelog.mdx | 4 ++++ 2 files changed, 7 insertions(+) diff --git a/references/api/api-keys.mdx b/references/api/api-keys.mdx index 9fc5d2d..1d694d4 100644 --- a/references/api/api-keys.mdx +++ b/references/api/api-keys.mdx @@ -47,10 +47,13 @@ Higher limits are available on request, applied per key: | Endpoint | Limit | | ---------------------- | ----------------------- | | `/quote` | 10 requests per second | +| `/requests/v3` | 20 requests per second | | `/requests` | 10 requests per second | | `/transactions/status` | 10 requests per second | | Other endpoints | 200 requests per minute | +`/requests` and `/requests/v2` share the 10 rps bucket; `/requests/v3` has its own 20 rps bucket. + To request higher limits, get in touch through the support widget in the [Relay Dashboard](https://dashboard.relay.link). ## How to Use an API key diff --git a/references/api/changelog.mdx b/references/api/changelog.mdx index 57e1255..5f5e3ac 100644 --- a/references/api/changelog.mdx +++ b/references/api/changelog.mdx @@ -3,6 +3,10 @@ title: "API Changelog" description: "Record of breaking changes, deprecations, and notable additions to the Relay API" --- +## 2026-07-28 — Higher elevated rate limit for `GET /requests/v3` + +**Added** — `GET /requests/v3`: the elevated per-key rate limit is now **20 requests per second**, up from the previously shared 10 rps bucket. `GET /requests` and `GET /requests/v2` continue at 10 rps. Default (non-elevated) limits are unchanged. See [Elevated Rate Limits](/references/api/api-keys#elevated-rate-limits). + ## 2026-07-27 — More specific `failReason` values for submission failures **Added** — `GET /requests/v3`, `GET /intents/status/v3`, and the `request.status.updated` webhook: the response `failReason` enum gains **`TRANSACTION_SUBMISSION_FAILED`**, returned when the fill transaction could not be broadcast to the network (RPC unavailable, signer unavailable, or pre-broadcast rejection — no transaction hash exists), and **`TRANSACTION_NOT_INCLUDED`**, returned when the fill transaction was broadcast but never included onchain before Relay's retry and gas-bump window elapsed. See [Handling Execution Errors](/references/api/api_core_concepts/execution-errors#transaction-construction--gas-errors) for the full enum.