> ## Documentation Index > Fetch the complete documentation index at: https://docs.vibechain.com/llms.txt > Use this file to discover all available pages before exploring further. # List collection activity > Returns collection events in descending chain order. Pass the returned block-number cursor to continue. Responses are cached for about 10 seconds. ## OpenAPI ````yaml /api-reference/vibemarket_openapi.yml get /collection/{contractAddress}/events openapi: 3.0.3 info: title: vibe.market API version: 1.0.0 description: | Production API for vibe.market packs, games, collections, creator drafts, allowlists, market activity, social features, recovery tools, and analytics. Most operations require a caller-specific VibeChain API key in the `API-KEY` header. Account-bound writes additionally require a vibe.market session token in `Authorization: Bearer `. Public or Bearer-only exceptions are marked on the individual operation. contact: name: VibeChain developer support email: gm@vibechain.com url: https://docs.vibechain.com/api-reference/vibemarket-intro servers: - url: https://build.vibechain.com/vibe/boosterbox description: Production security: - ApiKeyAuth: [] tags: - name: Packs description: Read pack ownership, state, rarity, and metadata. - name: Collections description: Read collection holdings, statistics, and activity. - name: Games description: Discover games and read launch configuration. - name: Metadata description: Read published metadata and update launched collections. - name: Creator drafts description: Create, autosave, inspect, confirm, and delete launch drafts. - name: Allowlists description: Configure draft allowlists and generate Merkle proofs. - name: Activity description: Read recent packs and recover indexed transaction events. - name: Social description: Read chat, react to messages, and report collections. - name: Analytics description: Read price history, leaderboards, and platform totals. - name: Utility description: Resolve slugs, regions, prices, and processing readiness. paths: /collection/{contractAddress}/events: get: tags: - Collections - Activity summary: List collection activity description: > Returns collection events in descending chain order. Pass the returned block-number cursor to continue. Responses are cached for about 10 seconds. operationId: listVibeMarketCollectionEvents parameters: - $ref: '#/components/parameters/ContractAddressPath' - $ref: '#/components/parameters/ChainId' - in: query name: eventTypes description: Comma-separated event types. schema: type: string example: buy,sell,mythic,opened - in: query name: limit schema: type: integer minimum: 1 maximum: 500 default: 100 - in: query name: cursor description: Block-number cursor returned by the preceding page. schema: type: integer minimum: 0 - in: query name: startDate schema: type: string format: date-time - in: query name: endDate schema: type: string format: date-time - in: query name: address description: Restrict activity to one wallet. schema: $ref: '#/components/schemas/EvmAddress' responses: '200': description: One activity page content: application/json: schema: $ref: '#/components/schemas/CollectionEventsResponse' '400': $ref: '#/components/responses/InvalidInput' '429': $ref: '#/components/responses/ApiKeyOrRateLimit' '500': $ref: '#/components/responses/InternalError' components: parameters: ContractAddressPath: in: path name: contractAddress required: true schema: $ref: '#/components/schemas/EvmAddress' ChainId: in: query name: chainId description: EVM chain ID. Defaults to Base mainnet. schema: type: integer minimum: 1 default: 8453 schemas: EvmAddress: type: string pattern: ^0x[a-fA-F0-9]{40}$ example: '0x1111111111111111111111111111111111111111' CollectionEventsResponse: type: object required: - success - events - pagination - stats - filters properties: success: type: boolean enum: - true events: type: array items: $ref: '#/components/schemas/CollectionEvent' pagination: type: object required: - limit properties: limit: type: integer next: type: string nullable: true description: Block-number cursor for the next page. stats: type: object required: - totalBuys - totalSells - totalPacksBought - totalPacksSold - mythicPulls - legendaryPulls - epicPulls - rarePulls properties: totalBuys: type: integer totalSells: type: integer totalPacksBought: type: integer totalPacksSold: type: integer mythicPulls: type: integer legendaryPulls: type: integer epicPulls: type: integer rarePulls: type: integer filters: type: object additionalProperties: true CollectionEvent: type: object required: - eventType - blockNumber additionalProperties: true properties: eventType: type: string enum: - booster_drops_minted - 100_packs_purchased - booster_drop_sold - booster_drop_sold_batch - rarity_assigned - booster_drop_opened - booster_drop_transfer - market_graduated - drop_created displayType: type: string example: Rarity Revealed displaySubType: type: string nullable: true contractAddress: $ref: '#/components/schemas/EvmAddress' txHash: $ref: '#/components/schemas/TransactionHash' blockNumber: type: integer createdAt: type: string format: date-time metadata: type: object additionalProperties: true users: type: object additionalProperties: $ref: '#/components/schemas/UserSummary' primaryActor: $ref: '#/components/schemas/UserSummary' pricePerPack: $ref: '#/components/schemas/Wei' rewardAmount: $ref: '#/components/schemas/Wei' Error: type: object required: - success - message properties: success: type: boolean enum: - false message: type: string error: description: >- Optional diagnostic detail. Do not depend on this field being present in production. oneOf: - type: string - type: object additionalProperties: true TransactionHash: type: string pattern: ^0x[a-fA-F0-9]{64}$ example: '0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa' UserSummary: type: object additionalProperties: true properties: id: type: string username: type: string displayName: type: string profileImage: type: string format: uri address: $ref: '#/components/schemas/EvmAddress' Wei: type: string pattern: ^[0-9]+$ description: Unsigned integer amount denominated in Wei. example: '1000000000000000' responses: InvalidInput: description: Invalid or incomplete request input content: application/json: schema: $ref: '#/components/schemas/Error' example: success: false message: Invalid contract address ApiKeyOrRateLimit: description: API key missing/invalid or the caller's rate allowance is exhausted content: application/json: schema: $ref: '#/components/schemas/Error' example: success: false message: >- Too many requests or invalid API key! See docs.vibechain.com for more info. InternalError: description: The server could not complete the operation content: application/json: schema: $ref: '#/components/schemas/Error' example: success: false message: Failed to complete request securitySchemes: ApiKeyAuth: type: apiKey in: header name: API-KEY description: Caller-specific VibeChain API key used for quota and abuse control. ````