> ## Documentation Index > Fetch the complete documentation index at: https://docs.0xmonaco.com/llms.txt > Use this file to discover all available pages before exploring further. # List funding payments > List funding payment history. Get the current user's private funding payment history with pagination and optional filters by market, margin account, and position. ## OpenAPI ````yaml /proto-openapi/api/openapi.yaml get /api/v1/accounts/funding-payments openapi: 3.0.3 info: title: Monaco Protocol API description: REST API for the Monaco Protocol hybrid CLOB exchange. version: 1.0.0 servers: - url: https://staging.apimonaco.xyz description: Staging server (Testnet) security: [] tags: - name: AccountsService - name: ApplicationsService - name: AuthService - name: BuildercodeRewardsService - name: CopyTradingService - name: DelegatedAgentsService - name: FaucetService - name: FeesService - name: HealthService - name: ManagedMarketsService description: |- Wallet-authenticated maker assignments. The signed session must match both configured maker user and application. Owner IDs are process fences, never auth. Only wallet sessions are supported; delegated-agent sessions receive 403. - name: MarginAccountsService description: |- Current public isolated-margin semantics: - a user has one parent margin account per application scope - opening orders create or reuse isolated position buckets under that parent - parent account creation is handled internally by margin workflows - name: MarketService - name: OrderbookService - name: OrdersService - name: PositionsService description: |- Current public isolated-margin semantics: - positions link to a parent margin account and, when applicable, a bucket id - opening orders create or reuse isolated position buckets under the parent - users can open another isolated position by reusing the parent account with a different market bucket - name: PulseService - name: SweeperService - name: TraderCodeService - name: TradesService - name: WhitelistService - name: WithdrawalsService paths: /api/v1/accounts/funding-payments: get: tags: - AccountsService - Accounts summary: List funding payments description: |- List funding payment history. Get the current user's private funding payment history with pagination and optional filters by market, margin account, and position. operationId: list_funding_payments parameters: - name: tradingPairId in: query schema: type: string minLength: 1 format: uuid description: Trading pair identifier (UUID) - name: positionId in: query schema: type: string - name: marginAccountId in: query schema: type: string - name: pageSize in: query schema: type: integer format: uint32 minimum: 1 maximum: 1000 default: 20 description: Items per page (max 1000) - name: pageToken in: query description: |- Pagination cursor with two states: - Omitted or empty string (""): start a cursor walk with no prior position, from the newest payment. - Non-empty: an opaque cursor from a previous response's `nextPageToken`; results resume immediately after that position. The walk seeks on `(created_at, id)` descending. Not `period_end`, which the removed page-number mode led its sort with: that column is nullable and the risk engine leaves it unset when a payment carries no window, while `created_at` is always stamped (it falls back to the settlement instant). The `id` tie-break is new — the removed order had none, so a page boundary inside one funding window could already repeat or drop a payment. `total` and `totalPages` are populated — bounded by the server count ceiling, see `totalCapped`. Filters must match the request that produced the token, or the request is rejected 400. schema: type: string responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/ListFundingPaymentsResponse' '400': description: Invalid request '401': description: Authentication required '429': description: >- Read rate limit exceeded — every authenticated read draws one request from the account's read budget; retry after the interval in details.retryAfter '500': description: Internal server error security: - monacoSignature: [] - monacoHttpSignature: [] components: schemas: ListFundingPaymentsResponse: type: object properties: records: type: array items: $ref: '#/components/schemas/FundingPaymentRecord' nullable: true total: example: 2 type: integer description: >- Number of funding payments matching the filter, bounded by the server ceiling — a lower bound when totalCapped is true. format: uint32 nullable: true pageSize: example: 20 type: integer description: Items per page format: uint32 nullable: true totalPages: example: 1 type: integer description: >- Number of pages at this pageSize, bounded by the server ceiling — a lower bound when totalCapped is true. format: uint32 nullable: true nextPageToken: type: string description: >- Cursor for the next page, minted from the last row of an over-fetched page: this listing is one ordered read, so a page shorter than `pageSize` proves the walk is exhausted and this is empty. nullable: true totalCapped: example: false type: boolean description: >- True when more than the server ceiling of payments matched, so the count stopped at the ceiling and total/totalPages are a lower bound. nullable: true FundingPaymentRecord: type: object properties: id: example: 123e4567-e89b-12d3-a456-426614174000 type: string description: Funding payment UUID format: uuid nullable: true positionId: example: 123e4567-e89b-12d3-a456-426614174000 type: string description: Margin position UUID format: uuid nullable: true marginAccountId: example: 123e4567-e89b-12d3-a456-426614174000 type: string description: Margin account UUID format: uuid nullable: true tradingPairId: example: 123e4567-e89b-12d3-a456-426614174000 type: string description: Trading pair UUID format: uuid nullable: true fundingRate: example: '0.0015' type: string description: Funding rate applied for the epoch nullable: true positionSize: example: '2' type: string description: Absolute position size at settlement nullable: true paymentAmount: example: '150' type: string description: >- Signed funding payment amount; positive means paid, negative means received nullable: true direction: example: PAID type: string description: Funding direction for the user nullable: true periodStart: example: '2026-04-07T10:00:00Z' type: string description: Funding window start timestamp (ISO 8601) nullable: true periodEnd: example: '2026-04-07T11:00:00Z' type: string description: Funding window end timestamp (ISO 8601) nullable: true createdAt: example: '2026-04-07T11:00:00Z' type: string description: Funding payment creation timestamp (ISO 8601) nullable: true securitySchemes: monacoSignature: type: apiKey description: >- Ed25519 session-key request signing. Every authenticated request carries three headers: `X-Monaco-PublicKey` (64-char lowercase-hex session public key), `X-Monaco-Timestamp` (Unix milliseconds, within 30s of server time), and `X-Monaco-Signature` (hex ed25519 signature). The signature is over `METHOD\npath?query\ntimestamp_ms\nSHA256_hex(body)`, where the body hash is the SHA-256 of the empty byte string when there is no body. Obtain the session keypair from `POST /api/v1/auth/challenge` followed by `POST /api/v1/auth/verify`. name: X-Monaco-Signature in: header monacoHttpSignature: type: apiKey description: >- RFC 9421 Ed25519 session-key request signatures. Send Signature-Input, Signature, and Content-Digest together; never combine them with X-Monaco-* credentials. The monaco signature covers @method, @path, @query, and content-digest in that order, with created (Unix seconds within 30s of server time), keyid (registered lowercase-hex session public key), and alg=ed25519 parameters. Content-Digest uses RFC 9530 sha-256 over the exact body bytes, including the empty body. Query coverage retains ordering and percent encoding. Timestamp freshness does not reject repeated identical requests; use endpoint idempotency where supported. Existing legacy signing remains supported during server-first migration; SDK RFC 9421 signing is opt-in. See https://docs.0xmonaco.com/reference/http-message-signatures for the complete profile and trust model. name: Signature in: header ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.