List funding payments
Retrieves historical funding payments for a portfolio.
Endpoint
GET /api/v1/funding-payments
Authentication
Device-key cookie or X-API-KEY header. The credential’s account must own the requested
portfolio, and a pinned credential may only read its own subaccount.
Returns
200 OKwith a JSON list ofFundingPaymentResponseobjects, ordered newest first.400 Bad Requestifmarketor the timestamps can’t be parsed.404 Not Foundif the portfolio does not exist under the authenticated account.
Authorizations
Base64-encoded API key issued by POST /api/v1/api-keys.
Query Parameters
x >= 0x >= 0Optional market symbol filter (e.g. BTC-PERP).
Optional lower bound on effective_at, in unix milliseconds (inclusive).
Optional upper bound on effective_at, in unix milliseconds (inclusive).
Maximum number of funding payments to return. Must be between 1 and 1000; defaults to 100.
1 <= x <= 1000Number of funding payments to skip from the start of the result set. Must be >= 0; defaults to 0.
x >= 0Response
Funding payments (newest first)
A system-generated unique identifier for an account.
x >= 0A unique identifier for a portfolio within a subaccount.
x >= 0A unique identifier for a subaccount within an account.
x >= 0The settled funding rate for the period, as a decimal string.
"0.0001"
The unique identifier of the funding payment
"0190b6c2-7e4a-7c3b-9f21-2b6a1c4e5d8f"
The symbol of the market (e.g. BTC-PERP)
"BTC-PERP"
The signed payment applied to the portfolio cash balance in USDC. Positive means the portfolio received funding; negative means it paid.
"-12.50"
The signed position size at the time of settlement (positive for long, negative for short), expressed in base-asset units.
"0.25"
The timestamp at which the funding payment was effective.
x >= 0