Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mobula.io/llms.txt

Use this file to discover all available pages before exploring further.

Alpha Preview — This endpoint is in alpha and may change without notice.

​
Overview

Query the lifecycle status of a bridge intent. You can look up by:
  • Intent ID — the bytes32 identifier generated on-chain (starts with 0x, 66 chars)
  • Deposit TX hash — the transaction hash of the deposit on the origin chain

​
Status Lifecycle

pending -> deposited -> filling -> filled -> settled
                          |
                          v
                       retrying -> refunded
                                      |
                                      v
                                    failed
StatusDescription
pendingIntent not yet detected — deposit may still be processing
depositedDeposit detected by chain listener
fillingFill transaction sent to destination chain
filledFill confirmed on destination — user has received funds
settledSettlement complete, solver has withdrawn deposited funds
retryingFill failed, retrying with backoff (up to 3 attempts)
refundedAll retries exhausted, user refunded on origin chain
failedRefund also failed — requires manual intervention

​
SDK Usage

import { Mobula } from "@mobula/sdk";

const mobula = new Mobula({ apiKey: "YOUR_API_KEY" });

// Poll by deposit TX hash
const status = await mobula.rest.fetchBridgeStatus({
  id: "0xYourDepositTxHash...",
});

console.log(status.data.status);      // "filled"
console.log(status.data.fillTxHash);  // destination chain TX hash
console.log(status.data.latencyMs);   // e.g. 487