> ## Documentation Index > Fetch the complete documentation index at: https://docs.messari.io/llms.txt > Use this file to discover all available pages before exploring further. # List Events > Paginated list of events. Events are logical groupings of related developments; the filter surface matches `/v2/developments` since downstream the service joins on the matching developments. Filter semantics also match: silent-drop on unresolved `assetIds` and unknown taxonomy slugs in `intelCategories` / `intelSubcategories`, 400 from `eventIds` on unresolvable tokens. Results are ordered most recent first. ## OpenAPI ````yaml GET /monitoring/v2/events openapi: 3.0.0 info: description: OpenAPI specification for the entire Messari API title: Messari API - Monitoring V2 version: 1.0.0 servers: - description: Messari API url: https://api.messari.io security: [] paths: /monitoring/v2/events: get: tags: - monitoring/v2 summary: List events description: >- Paginated list of events. Events are logical groupings of related developments; the filter surface matches `/v2/developments` since downstream the service joins on the matching developments. Filter semantics also match: silent-drop on unresolved `assetIds` and unknown taxonomy slugs in `intelCategories` / `intelSubcategories`, 400 from `eventIds` on unresolvable tokens. Results are ordered most recent first. operationId: listMonitoringEvents parameters: - in: query name: limit schema: type: integer format: int64 default: 10 example: 10 description: >- Page size, default 10. Coerced silently: values above 100 are capped to 100; values ≤ 0 (and missing/non-integer values) fall back to the default. - in: query name: page schema: type: integer format: int64 default: 1 example: 1 description: 1-indexed page (default 1) - in: query name: assetIds schema: type: string description: >- Comma-separated asset UUIDs or slugs. Unresolved tokens are silently dropped. - in: query name: eventIds schema: type: string description: >- Comma-separated event identifiers. Each token is either a UUID or the slug-with-id-prefix form returned in the `slug` field (e.g. `my-event-a1b2c3d4`). An unresolvable token returns 400; the offending token is quoted in the error message. - in: query name: intelCategories schema: type: string description: Comma-separated category slugs from /v2/categories - in: query name: intelSubcategories schema: type: string description: Comma-separated subcategory slugs from /v2/categories - in: query name: minimumImportance schema: type: string enum: - not-important - low - medium - high description: >- Minimum importance level (inclusive). Values: not-important, low, medium, high. - in: query name: verified schema: type: boolean description: Restrict to verified items - in: query name: actionable schema: type: boolean description: Restrict to actionable items - in: query name: governance schema: type: boolean description: Restrict to governance-related items - in: query name: assetSectors schema: type: string description: Comma-separated asset sectors - in: query name: assetSubsectors schema: type: string description: Comma-separated asset subsectors - in: query name: assetPreTge schema: type: boolean description: Restrict to pre-TGE assets - in: query name: assetEcosystemNetworkIds schema: type: string description: Comma-separated ecosystem network ids - in: query name: start schema: type: string description: >- Lower bound on the time window. Compares against `startedAt`. Accepts RFC3339, YYYY-MM-DD, or unix epoch seconds. - in: query name: end schema: type: string description: >- Upper bound on the time window. Compares against `startedAt`. Accepts RFC3339, YYYY-MM-DD, or unix epoch seconds. - in: query name: search schema: type: string description: Free-text search (max 200 chars) responses: '200': description: Default response content: application/json: schema: type: object properties: error: type: string nullable: true data: type: array items: $ref: '#/components/schemas/MonitoringEvent' metadata: $ref: '#/components/schemas/MonitoringPagination' required: - data example: error: null data: - id: cfcb4aa9-4a22-4f2a-aa9c-16009426f7c6 slug: marc-andr-dumas-joins-the-graph-council-cfcb4a title: Marc-André Dumas Joins The Graph Council summary: '' industry: crypto developmentCount: 1 documentCount: 4 startedAt: '2026-04-20T18:07:34Z' endedAt: '2026-04-20T18:07:34Z' createdAt: '2026-04-20T18:16:08Z' updatedAt: '2026-04-20T18:16:08Z' intelCategories: - team_and_operations intelSubcategories: - personnel_change importance: low verified: true actionable: false governance: false assets: - id: fcb726c7-364f-4252-8ee8-70b0bbbd8791 name: The Graph slug: the-graph symbol: GRT class: primary developments: - id: 87bb367e-dc20-43e1-839c-d93175d885f3 title: Marc-André Dumas Joins The Graph Council summary: >- The Graph Foundation has [announced](https://forum.thegraph.com/t/introducing-new-council-member-marc-andre-dumas/6919) the appointment of Marc-André Dumas to The Graph Council. Dumas is the founder of Ellipfra, a web3 and blockchain infrastructure firm, and previously served as Technical Lead at Chronicle Labs, where he developed and operated blockchain oracles for MakerDAO. He earlier held roles at MakerDAO, including Team Lead of Backend Services and Senior Integration Specialist, and led integration and engineering teams at Miranda Technologies. startedAt: '2026-04-20T18:07:34Z' endedAt: '2026-04-20T18:07:34Z' importance: low verified: true actionable: false governance: false intelCategories: - team_and_operations intelSubcategories: - personnel_change slug: development-87bb36 - id: cf1d1d61-49bf-42dd-b3cd-6cee0073965f slug: btc-e-mode-deprecation-on-sparklend-cf1d1d title: BTC e-mode Deprecation on SparkLend summary: '' industry: crypto developmentCount: 1 documentCount: 2 startedAt: '2026-04-20T18:03:26Z' endedAt: '2026-04-20T18:03:26Z' createdAt: '2026-04-20T18:16:07Z' updatedAt: '2026-04-20T18:16:07Z' intelCategories: - protocol_management intelSubcategories: - discontinuation importance: low verified: true actionable: false governance: false assets: - id: 0b3fee37-34e6-4ca0-a838-c5638fb1129f name: Coinbase Wrapped BTC slug: coinbase-wrapped-btc symbol: CBBTC class: primary - id: b09a349b-f941-4fff-8820-32398dd88839 name: Spark slug: spark-sky-protocol symbol: SPK class: primary developments: - id: 3c8ad9eb-6ab8-4233-a06d-5c0c09e9506c title: BTC e-mode Deprecation on SparkLend summary: >- Phoenix Labs has shared a [notice](https://forum.skyeco.com/t/april-20-2026-notice-of-btc-e-mode-deprecation-on-sparklend/27854) advising SparkLend users borrowing cbBTC through BTC e-mode to close their positions before Jun. 7, 2026 to avoid potential liquidations. SparkLend's BTC e-mode is expected to be deprecated "in the near future, subject to governance approval." startedAt: '2026-04-20T18:03:26Z' endedAt: '2026-04-20T18:03:26Z' importance: low verified: true actionable: false governance: false intelCategories: - protocol_management intelSubcategories: - discontinuation slug: development-3c8ad9 - id: a7b462c8-654d-4414-9c39-354e3e9f2ff1 slug: hpp-dao-a7b462 title: HPP DAO summary: '' industry: crypto developmentCount: 1 documentCount: 0 startedAt: '2026-04-20T17:43:47Z' endedAt: '2026-04-20T17:43:47Z' createdAt: '2026-04-20T17:56:37Z' updatedAt: '2026-04-20T17:56:37Z' intelCategories: - protocol_management intelSubcategories: - governance_update importance: low verified: true actionable: false governance: false assets: - id: 0ac4ace4-04c1-4f9a-9179-5b71813665a8 name: House Party Protocol slug: house-party-protocol symbol: HPP class: primary - id: 67a3996b-923a-41d1-ab52-fcb99190e138 name: Aergo slug: aergo symbol: AERGO class: secondary developments: - id: 3bb90ba9-c5eb-4891-8baa-0486e4f72a75 title: HPP DAO summary: >- The House Party Protocol (HPP) team has [launched](https://medium.com/aergo/hpp-dao-is-now-live-7f3350a32a48) HPP DAO, the protocol's on-chain governance system. The system is built in-house on a staking-based voting mechanism; HPP token stakers receive voting power based on a snapshot taken at the start of each voting period, with one vote per address per proposal. The team states the system was built internally to support integration with HPP's native XP and staking rewards systems, which third-party governance platforms could not accommodate. HPP DAO operates across three components: a Discourse forum for proposal discussion, a voting layer for on-chain and off-chain votes, and HPP Report, a governance summary publication. Proposals must pass through five sequential stages: Discussion, Formalization, Voting, Execution, and Integration; no stage may be skipped, and rejection at any stage ends that cycle with resubmission permitted. Governance participation is tracked via XP, which will be integrated with HPP's upcoming Staking Seasons to factor into staking rewards. The first governance proposal is expected shortly. startedAt: '2026-04-20T17:43:47Z' endedAt: '2026-04-20T17:43:47Z' importance: low verified: true actionable: false governance: false intelCategories: - protocol_management intelSubcategories: - governance_update slug: development-3bb90b metadata: limit: 3 page: 1 totalRows: 46199 totalPages: 15400 '400': description: Bad Request content: application/json: schema: type: object properties: error: type: string data: nullable: true required: - error '403': description: Forbidden content: application/json: schema: type: object properties: error: type: string data: nullable: true required: - error '500': description: Internal Server Error content: application/json: schema: type: object properties: error: type: string data: nullable: true required: - error security: - apiKey: [] components: schemas: MonitoringEvent: type: object description: >- Logical grouping of related developments. List-form Event responses embed a slim `developments` array, most recent first, so callers can render an event card without a follow-up request. The fully-hydrated Development shape is returned by `GET /v2/events/{eventId}` and the `/v2/developments` endpoints. Event-level fields are aggregated across the event's child developments: - `intelCategories`, `intelSubcategories` — set union of children's values. - `assets` — set union of children's assets, with `class` rolled up via primary-takes-precedence (an asset that is `primary` on any child is `primary` on the event). - `importance` — max across children using the order `not-important < low < medium < high`. - `documentCount` — sum of children's `documents[]` lengths. - `developmentCount` — number of child developments; matches the length of the embedded `developments` array. - `startedAt` / `endedAt` — earliest start and latest end across children. properties: id: type: string slug: type: string title: type: string summary: type: string industry: type: string verified: type: boolean intelCategories: type: array items: type: string intelSubcategories: type: array items: type: string importance: type: string enum: - not-important - low - medium - high actionable: type: boolean governance: type: boolean developmentCount: type: integer documentCount: type: integer startedAt: type: string format: date-time endedAt: type: string format: date-time createdAt: type: string format: date-time updatedAt: type: string format: date-time assets: type: array items: $ref: '#/components/schemas/MonitoringAsset' developments: type: array description: >- Slim developments under this event, ordered most recent first. Length matches `developmentCount`. items: $ref: '#/components/schemas/EventDevelopment' MonitoringPagination: type: object properties: limit: type: integer page: type: integer totalRows: type: integer totalPages: type: integer required: - limit - page - totalRows - totalPages MonitoringAsset: type: object description: >- An asset attached to a development or event. `class` is `primary` (the asset is the focus of the item) or `secondary` (the asset is mentioned but not the focus). Event-level class is rolled up across the event's child developments — primary takes precedence. properties: id: type: string example: fcb726c7-364f-4252-8ee8-70b0bbbd8791 name: type: string example: The Graph slug: type: string example: the-graph symbol: type: string example: GRT class: type: string enum: - primary - secondary example: primary EventDevelopment: type: object description: >- Slim development representation embedded on list-form Event responses. Carries enough fields to render without a follow-up call (title, summary, importance, verification flags, taxonomy) while staying small enough that a page of events with their developments fits in a single response. Use `GET /v2/developments` or `GET /v2/developments/{developmentId}` to fetch the fully-hydrated development (documents, assets, createdAt/updatedAt, parent event reference). properties: id: type: string slug: type: string title: type: string summary: type: string startedAt: type: string format: date-time endedAt: type: string format: date-time importance: type: string enum: - not-important - low - medium - high verified: type: boolean actionable: type: boolean governance: type: boolean intelCategories: type: array items: type: string intelSubcategories: type: array items: type: string securitySchemes: apiKey: in: header name: X-Messari-API-Key type: apiKey ````