Skip to content

docs(drift): draft from internal source #379

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ipeleg merged 1 commit into from
Jul 28, 2026
Merged

docs(drift): draft from internal source #379

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions references/api/api-keys.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 4 additions & 0 deletions references/api/changelog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading