Skip to content

docs(drift): draft from internal source #340

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

Open
pedromcunha wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs(drift): draft from internal source #340

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3bbd3cf
docs(drift): draft from internal source
Jun 16, 2026
181194a
Merge branch 'main' into docs-drift/src-1db97dd688-4c225b5
pedromcunha Jun 16, 2026
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
24 changes: 24 additions & 0 deletions features/deposit-addresses.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1234,6 +1234,30 @@ When a quote is regenerated (different amount, token, or chain), a new `requestI
curl -X GET "https://api.relay.link/requests/v2?depositAddress=<DEPOSIT_ADDRESS>&includeChildRequests=true"
```

When a regeneration happens, the original request stays under its original `requestId` and public status while the actual sweep and fill move under the regenerated request. To follow the handoff directly, read `data.supersededByRequestId` on the original request — it returns the regenerated `requestId` that now owns the fill lifecycle.

```bash
curl -X GET "https://api.relay.link/requests/v2?id=<ORIGINAL_REQUEST_ID>"
```

```json
{
"requests": [
{
"id": "<ORIGINAL_REQUEST_ID>",
"status": "pending",
"data": {
"supersededByRequestId": "<REGENERATED_REQUEST_ID>"
}
}
]
}
```

<Tip>
Use `supersededByRequestId` when you have the original `requestId` and want a direct pointer to the request that owns the fill. Use `includeChildRequests=true` when you want every related request in one response.
</Tip>

### Request-Level Status

Once you have a `requestId`, you can use [Get Status](/references/api/get-intents-status-v3) for detailed status polling:
Expand Down
Loading