Skip to main content
POST
Submit transaction

Headers

X-BRDG-Api-Key
string

Optional partner key for server integrators. With it, each wallet is rate limited under the partner rather than on the IP of the calling server (a call naming no wallet, per the userIp in the body), bounded by a partner-wide ceiling. Unknown or disabled keys are refused with 401. See rate limits.

Path Parameters

id
string
required
Pattern: ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$

Body

application/json
signedTransaction
string

The signed transaction, for BRDG to broadcast. Send this or txHash.

Required string length: 1 - 100000
txHash
string

The hash or signature of a transaction the wallet already sent. Send this or signedTransaction.

Required string length: 1 - 128
step
enum<string>

Which built step this transaction is. Usually main.

Available options:
approve,
fee,
main,
redeem
userIp

The end user's IP address, if the quote carried one.

Response

The transfer’s new state and the hash on record

transferId
string
required
status
string
required
txHash
string | null
required
step
enum<string>
required
Available options:
approve,
fee,
main,
redeem
accepted
boolean
required
verification
enum<string> | null
required
Available options:
verified,
pending,
unverified_no_rpc,
unverified_rpc_error,
refuted,
null