> ## 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. # Get user trade history > Get user trades. Get the authenticated user's trade history with pagination. Returns trades where the user was either maker or taker, with user-specific side and fee information. ## OpenAPI ````yaml /proto-openapi/api/openapi.yaml get /api/v1/accounts/trades 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/trades: get: tags: - AccountsService - Accounts summary: Get user trade history description: |- Get user trades. Get the authenticated user's trade history with pagination. Returns trades where the user was either maker or taker, with user-specific side and fee information. operationId: get_user_trades parameters: - name: pageSize in: query schema: type: integer format: uint32 minimum: 1 maximum: 1000 default: 20 description: >- Items per page (max: 100 in page-number mode; up to 1000 when pageToken is present) - name: tradingPairId in: query schema: type: string minLength: 1 format: uuid description: Trading pair identifier (UUID) - 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 row. - Non-empty: an opaque cursor from a previous response's `nextPageToken`; results resume immediately after that position. Every walk covers full trade history — hot and archived rows merged. An unfiltered response carries a bounded item count (`total`); a response filtered by `trading_pair_id` carries none. Filters must match the request that produced the token. schema: type: string responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/GetUserTradesResponse' '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: GetUserTradesResponse: type: object properties: trades: type: array items: $ref: '#/components/schemas/UserTrade' nullable: true pageSize: example: '20' type: string description: Items per page nullable: true nextPageToken: type: string description: >- Cursor for the next page. Present whenever that page returned any rows (AIP-158 "maybe more" semantics), not only when the page is exactly full. Empty only when a page returned zero rows, which is the sole proof the walk is exhausted; a non-empty token does not guarantee further results, so keep following it until a response returns zero rows and an empty token. nullable: true total: example: 150 type: integer description: >- Number of trades a full walk returns, hot and archived, with a self-trade counted once; bounded by the server ceiling (10,000), a lower bound when totalCapped is true. Can briefly differ from a walk while the read replica catches up. Absent when tradingPairId filters the request or the count ran out of time: treat absent as unknown. format: uint32 nullable: true totalPages: example: 8 type: integer description: >- Number of pages at this pageSize, from the same bounded count as total; a lower bound when totalCapped is true. Absent exactly when total is. format: uint32 nullable: true totalCapped: example: false type: boolean description: >- True when more than the server ceiling of trades matched, so the count stopped at the ceiling and total/totalPages are a lower bound. False when total is exact, including exactly the ceiling, and when total is absent. nullable: true UserTrade: type: object properties: tradeId: type: string nullable: true orderId: type: string nullable: true format: uuid positionId: type: string nullable: true tradingPairId: type: string nullable: true format: uuid side: type: string nullable: true price: type: string nullable: true quantity: type: string nullable: true liquidityRole: type: string nullable: true fee: type: string description: >- Total fee this user paid on the trade, in raw quote units: for a taker, Monaco's taker fee plus the frontend's builder fee; for a maker, the maker fee (negative for a rebate). Equals `monaco_fee + builder_fee`. nullable: true realizedPnl: type: string nullable: true timestamp: type: string nullable: true monacoFee: type: string description: Monaco's component of `fee`, in raw quote units. nullable: true builderFee: type: string description: >- The frontend's builder fee component of `fee`, in raw quote units. Always "0" for a maker: builder fees are charged to takers only. 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.