List liabilities

GET 
/v1/liabilities

List your bank's issuer-side liabilities: for each other bank that holds your issued asset, how much it holds and how much of that is locked for settlement.

The caller is always the issuer: only holdings where your bank is the issuer and another bank is the holder are returned, and only while the holding registration is active. Each liability is the same holding, with the same amounts, that the holder sees as an exposure in GET /v1/exposures (the resource id has the two bank IDs swapped). A holder calling this endpoint does not see its exposures here; a bank whose asset no other bank holds gets 200 OK with an empty data array (never 404). Exposure limits are the holder-side view and are not repeated here.

Amounts are defined in the Liability schema. Response-level meta gives the ledger cut every entry on this page was read at and whether the read is current (see PositionReadMetadata); it is omitted when the page is empty.

Required scope: connector:liabilities:list.

Order. Ascending by holding_bank_id, then by root asset.

Request

Responses

200

One page of liabilities where the calling bank is the issuer (possibly empty).

400

The request is malformed: invalid JSON syntax, an invalid path or query parameter, a missing required header such as Idempotency-Key, or a single field that fails its own format rule. Fix the request before retrying; retrying it unchanged fails again.

401

The bearer token is missing, malformed, expired, signed by an unknown key, or was not issued by the platform IAM for the Lyriq Connector. Obtain a new token and retry. See the Authentication section.

403

The token is valid but may not perform this request: it lacks the required scope, has no bank membership, needs an x-dan-bank-id header to choose between several memberships, names a bank in x-dan-bank-id it has no membership for, or the caller's bank is suspended or terminated. A new token with the same configuration fails the same way. See the Authentication section.

429

The request was refused because a rate limit was reached (code RATE_LIMITED). No Retry-After header is sent; retry with exponential backoff.

503

The request could not be served right now. Either the network is not fully operational (OUTBOUND_HALTED or READ_ONLY: mutations are refused while read endpoints keep working; OPERATIONAL_STATE_UNKNOWN: the state could not be determined), or a platform dependency is temporarily unavailable. No Retry-After header is sent; retry later with backoff. When retrying a mutation, reuse the same Idempotency-Key and body.