How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bridge Liquidation Addresses API

The Liquidation Addresses API from Bridge — 8 operation(s) for liquidation addresses.

Bridge Liquidation Addresses API is one of 24 APIs that Bridge publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Liquidation Addresses. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 10 operations across 8 paths, and defines 45 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against a single base URL, https://api.bridge.xyz/v0.

10 operations 8 paths 45 schemas 7 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://api.bridge.xyz/v0
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Bridge Liquidation Addresses API declares 1 security scheme for authenticating requests. An API key is passed in the header as Api-Key (ApiKey). By default, every request must be authenticated.

Paths & Operations 10

Across 8 paths, the API surfaces 10 operations — 7 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Liquidation Addresses 10
POST
/customers/{customerID}/liquidation_addresses
Create a Liquidation Address
2 params body → 201401400500
GET
/customers/{customerID}/liquidation_addresses
Get all Liquidation Addresses for a customer
4 params → 200401400500
GET
/liquidation_addresses
Get all Liquidation Addresses
3 params → 200401400500
GET
/customers/{customerID}/liquidation_addresses/{liquidationAddressID}
Get a Liquidation Address
2 params → 200401400404500
PUT
/customers/{customerID}/liquidation_addresses/{liquidationAddressID}
Update a Liquidation Address
2 params body → 200401400500
GET
/customers/{customerID}/liquidation_addresses/{liquidationAddressID}/drains
Get drain history of a Liquidation Address
9 params → 200401400500
POST
/customers/{customerID}/liquidation_addresses/{liquidationAddressID}/drains/{drainID}/execute
Execute a pending USDT trade on a drain
4 params → 200400401404500
GET
/customers/{customerID}/liquidation_addresses/{liquidationAddressID}/balancesdeprecated
Get the balance of a Liquidation Address (deprecated)
2 params → 200401400500
GET
/liquidation_addresses/drains
Liquidation Address Activity Across All Customers
7 params → 200401400500
GET
/liquidation_addresses/drains/pending
List drains with pending USDT trades
5 params → 200400401500

Schemas 45

The contract defines 45 schemas that model the data the API accepts and returns. The most detailed are LiquidationAddress (24 properties), CreateLiquidationAddress (18 properties), Drain (17 properties), DrainDestination (17 properties). Each schema is shown below with its type and property counts.

TravelRuleWalletAttestedOwnershipAt
string
Required when wallettype is self-custodied or hosted. Must be a timestamp in the past indicating when wallet ownership was attested.
LiquidationAddressSourceChain
string
Currency
string
TransactionStatus
string
TravelRuleData
object
Travel Rule data for a crypto movement. Send this on create or update when the same counterparty should apply to every future use of a reusable resource, or se…
2 properties
EuroInclusiveCurrency
string
SepaSwiftInclusivePaymentRail
string
DrainReceipt
object
9 properties 7 required
SepaReference
string
A reference message to be sent with a SEPA transaction. We recommend you set a unique value to help you and your customers track payments end to end. It must b…
IdentifyingInformation
array
Drain
object
17 properties 6 required
CreateLiquidationAddress
object
18 properties 2 required
AchReference
string
A reference message to be sent with an ACH transaction. It can be at most 10 characters, A-Z, a-z, 0-9, and spaces.
FasterPaymentsReference
string
TravelRuleName
string
Legal name of the originator or beneficiary. Usually omitted when isself is true.
TransactionId
string
Deprecated: use trackingnumber instead. The unique transaction identifier for this payment.
TrackingNumber
string
The primary tracking identifier for this fiat transaction. Format varies by payment rail (e.g., UETR for SEPA/FPS, clave de rastreo for SPEI, end-to-end ID for…
LiquidationAddressCustomDeveloperFeePercent
stringnull
The developer fee percent that will be applied to this Liquidation Address or null to use the default fee. The value is a base 100 percentage, i.e. 10.2% is 10…
DrainDestination
object
17 properties 2 required
PixReference
string
Uetr
string
Deprecated: use trackingnumber instead. The unique end-to-end transaction reference, for tracing purposes.
Id
string
A UUID that uniquely identifies a resource
TravelRuleAddress
object
Address for travel rule submissions. All fields are optional to support partial address data (e.g. country-only).
6 properties
DrainReturnDetails
object
2 properties
Reference
A payment reference message for newer payment rails (e.g. Pix and Faster Payments).
PaymentRail
string
TraceNumber
string
The trace number of an ACH transfer
CreateLiquidationAddressResponse
4 required
LiquidationAddressSourceCurrency
string
TravelRuleWalletType
string
Indicates the custody model for the wallet. Use selfcustodied for customer-owned wallets (customer controls private keys), hosted for wallets managed by a deve…
Imad
string
(Wire only) The IMAD of a wire transfer, if available
UpdateLiquidationAddress
object
9 properties
WireMessage
string
A message to be sent with a wire transfer. It can have up to 140 characters. This message will be validated against 4 lines, each with a max length of 35 chara…
Balance
object
2 properties
Error
object
3 properties 2 required
LiquidationAddress
object
24 properties 10 required
ExchangeDetails
object
Exchange information for a currency conversion.
5 properties
LiquidationAddressGlobalDeveloperFeePercent
object
The developer fee percent that will be default applied to all Liquidation Addresses.
1 property
TravelRuleOriginator
object
Travel Rule details for originator crypto movement.
9 properties
SwiftReference
string
A payment reference message or remittance information to be included in a SWIFT transaction. It can have at most 4 lines (separated by "\n"), each line with a…
ReturnInstructions
object
Optional instructions for where to send funds if the transfer is returned (e.g. refund). Only supported when the source payment rail is crypto. Memo is require…
2 properties 1 required
PlaceOfBirthInput
object
Country (and optionally city) of birth. EEA / BBSA in-scope customers: supply when onboarding individuals or associated persons under the [EEA updated requirem…
2 properties
TravelRuleBeneficiary
object
Travel Rule details for beneficiary crypto movement.
6 properties
TravelRuleIsSelf
boolean
Set to true when this party is the same person or business as the Bridge customer on the resource. When true, Bridge uses the customer's name and address on fi…
SpeiReference
string
A payment reference message or remittance information to be included in a SPEI transaction. The allowed characters are alphanumeric a-z, A-Z, 0-9, and space

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bridge-liquidation-addresses-api-openapi.yml Raw ↑

Other APIs Bridge publishes across the network.

Bridge API Keys API
Bridge Associated Persons API
Bridge Batch Settlements API
Bridge Bridge Wallets API
Bridge Cards API
Bridge Crypto Return Policies API
Bridge Customers API
Bridge Developers API
Bridge Exchange Rates API
Bridge External Accounts API
Bridge Fiat Payout Configuration API
Bridge Funds Requests API
Where this information came from

This is an independent, third-party profile of Bridge Liquidation Addresses API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.