> ## 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. # Liquidation Events > Stored liquidation events for one market. Wallet-addressed events are newest-first and keyset-paged; event and side-summary reads remain separate so clients can fetch either surface independently. ## OpenAPI ````yaml /proto-openapi/api/openapi.yaml get /api/v1/market/pairs/{tradingPairId}/liquidation-events 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/market/pairs/{tradingPairId}/liquidation-events: get: tags: - MarketService - Market summary: Liquidation Events description: |- Stored liquidation events for one market. Wallet-addressed events are newest-first and keyset-paged; event and side-summary reads remain separate so clients can fetch either surface independently. operationId: list_liquidation_events parameters: - name: tradingPairId in: path required: true schema: type: string default: 893d2add-2f36-4ee7-b660-893d2add2f36 example: 893d2add-2f36-4ee7-b660-893d2add2f36 - name: startTime in: query schema: type: integer minimum: 0 maximum: 4102444800000 format: int64 description: Start time as Unix timestamp (milliseconds) - name: endTime in: query schema: type: integer minimum: 0 maximum: 4102444800000 format: int64 description: End time as Unix timestamp (milliseconds) - name: pageSize in: query schema: type: integer format: uint32 minimum: 1 maximum: 1000 default: 50 description: Events per page (max 1000) - name: pageToken in: query description: >- Opaque keyset cursor from the previous response. The token is bound to this pair and the requested time filters. schema: type: string responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/ListLiquidationEventsResponse' '400': description: Invalid liquidation-event filter or page token '404': description: Trading pair not found '500': description: Internal server error components: schemas: ListLiquidationEventsResponse: type: object properties: tradingPairId: type: string description: Trading pair UUID format: uuid nullable: true events: type: array items: $ref: '#/components/schemas/LiquidationEvent' description: >- Events in reverse chronological order (newest first). Each row contains only public event fields. nullable: true pageSize: example: 50 type: integer description: Number of events requested for this page format: uint32 nullable: true nextPageToken: type: string description: >- Opaque cursor for the next page; empty when the page is the end of the ordered result nullable: true LiquidationEvent: type: object properties: eventId: type: string description: >- Stable identifier of the stored liquidation event; use it to deduplicate REST backfills and WebSocket updates format: uuid nullable: true timestamp: example: 1736742000123 type: integer description: Event time as Unix milliseconds format: int64 minimum: 0 nullable: true tradingPairId: type: string description: Trading pair UUID format: uuid nullable: true wallet: example: '0x1234567890abcdef1234567890abcdef12345678' type: string description: Public wallet address associated with the liquidated position nullable: true side: example: LONG enum: - LONG - SHORT type: string description: 'Liquidated position side: LONG or SHORT' nullable: true positionSize: example: '0.25' type: string description: Absolute position size in base-asset units nullable: true markPrice: example: '95410.25' type: string description: Mark price captured for this event, in quote units per base unit nullable: true markNotional: example: '23852.5625' type: string description: >- Position size multiplied by the event-time mark price, in quote-asset units; no USD FX conversion nullable: true quoteAssetSymbol: example: USDC type: string description: Quote asset denomination of markNotional nullable: true description: >- One public per-position liquidation event. markNotional is positionSize multiplied by the mark price captured with the event, in quote-asset units. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.