From 3bbd3cfdfad01dd1a3129707af5b00a6d27606db Mon Sep 17 00:00:00 2001
From: relay-docs-bot <relay-docs-bot@users.noreply.github.com>
Date: Tue, 16 Jun 2026 03:13:01 +0000
Subject: [PATCH] docs(drift): draft from internal source

Requested by @cucupac via /publish-docs-pr
---
 features/deposit-addresses.mdx | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/features/deposit-addresses.mdx b/features/deposit-addresses.mdx
index 4c92408..7e3e3ec 100644
--- a/features/deposit-addresses.mdx
+++ b/features/deposit-addresses.mdx
@@ -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: