curl --request POST \
--url https://api.brdg.now/v1/bridge/transfers/{id}/submit \
--header 'Content-Type: application/json' \
--data '
{
"signedTransaction": "<string>",
"txHash": "<string>",
"userIp": "<string>"
}
'const options = {
method: 'POST',
headers: {'Content-Type': 'application/json'},
body: JSON.stringify({signedTransaction: '<string>', txHash: '<string>', userIp: '<string>'})
};
fetch('https://api.brdg.now/v1/bridge/transfers/{id}/submit', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.brdg.now/v1/bridge/transfers/{id}/submit"
payload = {
"signedTransaction": "<string>",
"txHash": "<string>",
"userIp": "<string>"
}
headers = {"Content-Type": "application/json"}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"transferId": "<string>",
"status": "<string>",
"txHash": "<string>",
"step": "approve",
"accepted": true,
"verification": "verified"
}{
"error": {
"code": "<string>",
"message": "<string>",
"details": {},
"retryAfterMs": 123
}
}{
"error": {
"code": "<string>",
"message": "<string>",
"details": {},
"retryAfterMs": 123
}
}{
"error": {
"code": "<string>",
"message": "<string>",
"details": {},
"retryAfterMs": 123
}
}{
"error": {
"code": "<string>",
"message": "<string>",
"details": {},
"retryAfterMs": 123
}
}{
"error": {
"code": "<string>",
"message": "<string>",
"details": {},
"retryAfterMs": 123
}
}{
"error": {
"code": "<string>",
"message": "<string>",
"details": {},
"retryAfterMs": 123
}
}Submit transaction
Accepts either a signed transaction for BRDG to broadcast (signedTransaction) or the hash of a transaction the wallet already sent (txHash). Send exactly one. BRDG decodes the transaction and compares it with the steps it built, and refuses anything that does not match without broadcasting it. Submitting the same transaction again returns the hash on record with accepted: false.
curl --request POST \
--url https://api.brdg.now/v1/bridge/transfers/{id}/submit \
--header 'Content-Type: application/json' \
--data '
{
"signedTransaction": "<string>",
"txHash": "<string>",
"userIp": "<string>"
}
'const options = {
method: 'POST',
headers: {'Content-Type': 'application/json'},
body: JSON.stringify({signedTransaction: '<string>', txHash: '<string>', userIp: '<string>'})
};
fetch('https://api.brdg.now/v1/bridge/transfers/{id}/submit', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.brdg.now/v1/bridge/transfers/{id}/submit"
payload = {
"signedTransaction": "<string>",
"txHash": "<string>",
"userIp": "<string>"
}
headers = {"Content-Type": "application/json"}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"transferId": "<string>",
"status": "<string>",
"txHash": "<string>",
"step": "approve",
"accepted": true,
"verification": "verified"
}{
"error": {
"code": "<string>",
"message": "<string>",
"details": {},
"retryAfterMs": 123
}
}{
"error": {
"code": "<string>",
"message": "<string>",
"details": {},
"retryAfterMs": 123
}
}{
"error": {
"code": "<string>",
"message": "<string>",
"details": {},
"retryAfterMs": 123
}
}{
"error": {
"code": "<string>",
"message": "<string>",
"details": {},
"retryAfterMs": 123
}
}{
"error": {
"code": "<string>",
"message": "<string>",
"details": {},
"retryAfterMs": 123
}
}{
"error": {
"code": "<string>",
"message": "<string>",
"details": {},
"retryAfterMs": 123
}
}Headers
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
^[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
The signed transaction, for BRDG to broadcast. Send this or txHash.
1 - 100000The hash or signature of a transaction the wallet already sent. Send this or signedTransaction.
1 - 128Which built step this transaction is. Usually main.
approve, fee, main, redeem The end user's IP address, if the quote carried one.
Response
The transfer’s new state and the hash on record
approve, fee, main, redeem verified, pending, unverified_no_rpc, unverified_rpc_error, refuted, null