1. Get Bridge Transaction Status
To check the status of a specific bridge, use the following API request:getBridgeStatus.js
quoteId
that you can use to track the transaction status.
Possible state values:
Bridge (non‑swap) flowsPENDING
– Quote committed; we’re waiting for a deposit on the source chain.PENDING_CONFIRMATION
– Fast chains only (WebSocket monitored). We’ve detected the deposit and are waiting for network confirmations. Not every bridge moves through this state.ACCEPTED
– We’ve detected the deposit and are executing on the destination chain.EXECUTED
– Bridge is complete; funds are credited on the destination chain.CANCELLED
– Cosmetic state. Can occur only if the user cancels a pending bridge via API. If the deposit later arrives, the bridge will move out of this state and be executed. Useful for hiding pending records you no longer intend to fund.FAILED
– Rare, manual state. Used only when there’s a specific issue and no way to complete the bridge. The user should contact Customer Support for a refund if one hasn’t already been issued.
DEPOSIT_ACCEPTED
– We’ve accepted the deposit and are performing a pre‑swap on the source chain (occurs beforeACCEPTED
).SWAP_FAILED
– The swap failed; we’ll look into issuing a refund.SWAP_FAILED_REFUNDED
– The swap failed and a refund was successfully issued.
2. Get Bridge History
To retrieve a list of past transactions:rhino.fi prioritizes transaction privacy, so the history endpoint is disabled by default for API keys.
If access is required, ensure your API key is kept private and properly configured.You can request access to the user history endpoint by contacting us.
getBridgeUserHistory.js
Next Steps
- If you haven’t integrated the bridge yet, start with the Quickstart Guide.
- For contract-level interactions, see Contract Examples.