> ## 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 movements > Get user movements. Get the current user's ledger movements (transaction history) with pagination and filtering support. ## OpenAPI ````yaml /proto-openapi/api/openapi.yaml get /api/v1/accounts/movements 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/movements: get: tags: - AccountsService - Accounts summary: Get user movements description: |- Get user movements. Get the current user's ledger movements (transaction history) with pagination and filtering support. operationId: get_user_movements parameters: - name: pageSize in: query schema: type: integer format: uint32 minimum: 1 maximum: 1000 default: 20 description: Items per page (max 1000) - name: transactionType in: query schema: type: string enum: - DEPOSIT - WITHDRAWAL - TRADE - FEE - FUNDING - LIQUIDATION - INTEREST - REWARD - CHAIN_SYNC minLength: 1 description: Transaction type - name: entryType in: query schema: type: string enum: - CREDIT - DEBIT - LOCK - UNLOCK - FEE minLength: 1 description: Ledger entry type - name: assetId in: query schema: type: string minLength: 1 format: uuid description: Asset identifier (UUID) - name: orderBy in: query schema: type: string default: DESC enum: - ASC - DESC minLength: 1 description: Sort direction for createdAt - 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 (or the oldest, when `orderBy` is ASC). - Non-empty: an opaque cursor from a previous response's `nextPageToken`; results resume immediately after that position. Every walk covers the ledger and funding arms merged. `total` and `totalPages` are populated — bounded by the server count ceiling, see `totalCapped`. Filters and `orderBy` 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/GetMovementsResponse' '400': description: Invalid request '401': description: Authentication required '404': description: User not found '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: GetMovementsResponse: type: object properties: movements: type: array items: $ref: '#/components/schemas/LedgerMovement' nullable: true total: example: 150 type: integer description: >- Number of movements 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: 8 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. Each arm of the union is cut at the same over-fetched depth and the outer query orders the merged rows, so a page shorter than `pageSize` means both arms are exhausted and this is empty — a non-empty token always has at least one further row behind it. nullable: true totalCapped: example: false type: boolean description: >- True when more than the server ceiling of movements matched, so the count stopped at the ceiling and total/totalPages are a lower bound. False when total is exact, including exactly the ceiling. nullable: true LedgerMovement: type: object properties: id: example: 123e4567-e89b-12d3-a456-426614174000 type: string description: Movement UUID format: uuid nullable: true entryType: example: CREDIT type: string description: 'Ledger entry type: CREDIT, DEBIT, LOCK, UNLOCK, or FEE' nullable: true transactionType: example: DEPOSIT type: string description: 'Transaction type: DEPOSIT, WITHDRAWAL, TRADE, or FEE' nullable: true amount: example: '100.50' type: string description: Human-readable amount in token units nullable: true token: example: '0x6a86da986797d59a839d136db490292cd560c131' type: string description: Token contract address nullable: true balanceBefore: example: '900.00' type: string description: Available balance before this movement nullable: true balanceAfter: example: '1000.50' type: string description: Available balance after this movement nullable: true lockedBefore: example: '50.00' type: string description: Locked balance before this movement nullable: true lockedAfter: example: '75.00' type: string description: Locked balance after this movement nullable: true referenceId: example: ref_123456 type: string description: ID of the related entity (order, trade, etc.) nullable: true referenceType: example: deposit type: string description: Type of the referenced entity nullable: true description: example: USDC deposit type: string description: Human-readable description of the movement nullable: true txHash: example: 0xabc123... type: string description: On-chain transaction hash (if applicable) nullable: true blockNumber: example: '18500000' type: string description: Block number of the on-chain transaction nullable: true createdAt: example: '2023-11-13T10:30:00Z' type: string description: Movement timestamp (ISO 8601) nullable: true symbol: example: USDC type: string description: Token symbol nullable: true decimals: example: 6 type: integer description: Token decimal places format: int32 nullable: true amountRaw: example: '100500000' type: string description: Raw amount in smallest token unit (no decimals) nullable: true balanceBeforeRaw: example: '900000000' type: string description: Raw available balance before this movement nullable: true balanceAfterRaw: example: '1000500000' type: string description: Raw available balance after this movement nullable: true lockedBeforeRaw: example: '50000000' type: string description: Raw locked balance before this movement nullable: true lockedAfterRaw: example: '75000000' type: string description: Raw locked balance after this movement nullable: true assetId: example: 123e4567-e89b-12d3-a456-426614174000 type: string description: Asset UUID format: uuid nullable: true userId: example: 123e4567-e89b-12d3-a456-426614174000 type: string description: User UUID who owns this movement format: uuid nullable: true balanceId: example: 123e4567-e89b-12d3-a456-426614174000 type: string description: Balance UUID this movement affects format: uuid 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.