execution status for a deposit address

[15august]

Hi team!

when using /quote/v2 deposit addresses to accept user deposits into app
From the docs:

• The same depositAddress is returned for the same route
• A single deposit address can be reused safely for that route
• Each /quote/v2 call returns a new requestId

product flow is:

• We generate a deposit address once per user per route
• Users may reuse this address multiple times for deposits
• Each deposit is a separate on-chain transaction

Q/P:
Users will not always initiate a new /quote/v2 request before sending funds, so in many cases we do not have a new requestId available upfront to track the deposit lifecycle

Because of this, it would be much simpler to:

• Track a deposit address directly
• Poll or query an API that returns:

• all deposits received by a given depositAddress
• their execution / bridge status
• source tx hash → destination tx hash mapping (if available)

Q:
Is there (or are there plans for) an API that allows querying all recent deposits and their statuses for a given deposit address, without requiring a requestId per deposit?

Would be really useful

[pedromcunha]

Hey, thanks for your valuable feedback. I'm going to check in with our team on this and I'll get back to you.

[15august]

Sure, thanks

I just see that possible to track user addresses and all transaction via [https://api.relay.link/requests/v2?user=](https://api.relay.link/requests/v2?user=)

But it's not working for deposit addresses, so would be great to track them too to match transactions

[pedromcunha]

We're seeing more deposit address usage and are planning on improving that feature. Your suggestion is being considered by the team. I'll keep you posted on the progress we make.

[15august]

@pedromcunha do you have any ETA?

[pedromcunha]

Hi, so the team suggested using the requests/v2 api as you mentioned but there's a bug there we're currently working on fixing. I'll make sure to get back to you when it's patched. If I don't reach out in a week or so please touch base with me here. Thanks

[15august]

@pedromcunha gently pinging on this task here:)

[pedromcunha]

Hi, we're patching up the bugs you mentioned with the requests api when filtering by deposit address but that is now the recommended approach moving forward. Also fyi requestIds generated by the deposit address flow will be regenerated just in time so keep this in mind when building your integration.

The fix should land this week, although most of the team is at an offsite so it may get pushed to next week. Appreciate your patience.