Loading video...
Video Failed to Load
Complete visibility into your onchain payments with Requests v3 At real volume, the gap between what happened and what you can see is an operational problem. The Requests page in the Relay Dashboard now closes it: near real-time data on every request, filters you can compose across status, chains,... show more
10,832 views • 1 month ago •via X (Twitter)
16 Comments

Under the hood: Requests v3, rebuilt on Elasticsearch. One term finds any request: ID, wallet, deposit address, or any tx hash. Near real-time data that v2 couldn't give you. Cleaner responses with quoted vs actual on every fee. Per-key access, so heavy usage never slows anyone else. Everything the Dashboard can do, your own tooling can do directly via GET /requests/v3.

requests/v2 is deprecated as of today, with a 4-month migration window before it retires. The migration guide covers every change, and updated SDKs (RelayClient and RelayKit) do most of the work: Note: Requests v3 authenticates with an API key. Create one in the Dashboard.

LFR💜🥺

add arc bridge @RelayProtocol pls!!

Please add @arc bridge

Should active users expect any airdrop?

@RelayProtocol Hi Team, we added Relay to XFlow ( our cross-chain explorer. The data doesn't quite add up. Worth comparing analytics to see why?

when we can bridge to ARC?

when adding tokenized stocks on RH?

gRelay 💜

Users that are affected are eligible for compensation as part of our previously approved TOS policy Support Dashboard:

When arc?

pls we need @arc

Affected users are eligible for compensation as part of our previously approved TOS policy. If you are affected, compensation management is available on our Support Dashboard below ⤵️

Users that are affected are eligible for compensation as part of our previously approved TOS policy If you are affected, Support Dashboard:

Users that are affected are eligible for compensation as part of our previously approved TOS policy If you are affected here is our Support Dashboard:
