Chainstack

Chainstack Events API

The Events API from Chainstack — 1 operation(s) for events.

Documentation GitHub OpenAPI

Documentation

https://docs.chainstack.com/reference/platform-api-getting-started

https://docs.chainstack.com/reference/ethereum-getting-started

https://docs.chainstack.com/reference/ethereum-beacon-chain-api-getting-started

https://docs.chainstack.com/reference/solana-getting-started

https://docs.chainstack.com/reference/bitcoin-getting-started

https://docs.chainstack.com/reference/bnb-chain-getting-started

https://docs.chainstack.com/reference/polygon-getting-started

https://docs.chainstack.com/reference/arbitrum-getting-started

https://docs.chainstack.com/reference/optimism-getting-started

https://docs.chainstack.com/reference/base-getting-started

https://docs.chainstack.com/reference/avalanche-getting-started

https://docs.chainstack.com/reference/fantom-getting-started

https://docs.chainstack.com/reference/gnosis-getting-started

https://docs.chainstack.com/reference/cronos-getting-started

https://docs.chainstack.com/reference/aurora-getting-started

https://docs.chainstack.com/reference/ronin-getting-started

https://docs.chainstack.com/reference/tron-getting-started

https://docs.chainstack.com/reference/ton-getting-started

https://docs.chainstack.com/reference/starknet-getting-started

https://docs.chainstack.com/reference/zksync-getting-started

https://docs.chainstack.com/reference/polygon-zkevm-getting-started

https://docs.chainstack.com/reference/hyperliquid-getting-started

https://docs.chainstack.com/reference/monad-getting-started

https://docs.chainstack.com/reference/plasma-getting-started

https://docs.chainstack.com/reference/tempo-getting-started

Specifications

https://raw.githubusercontent.com/api-evangelist/chainstack/refs/heads/main/openapi/chainstack-events-api-openapi.yml

https://raw.githubusercontent.com/api-evangelist/chainstack/refs/heads/main/asyncapi/chainstack-asyncapi.yml

Schemas & Data

https://raw.githubusercontent.com/api-evangelist/chainstack/refs/heads/main/json-schema/chainstack-node-schema.json

https://raw.githubusercontent.com/api-evangelist/chainstack/refs/heads/main/json-schema/chainstack-jsonrpc-envelope-schema.json

Other Resources

https://raw.githubusercontent.com/api-evangelist/chainstack/refs/heads/main/json-ld/chainstack-context.jsonld

OpenAPI Specification

openapi: 3.0.3
info:
  title: Chainstack Arbitrum Node Account Info Events API
  version: 1.0.0
  description: Chainstack-managed RPC node API for the Arbitrum blockchain. Endpoints follow the canonical JSON-RPC over HTTPS interface for the network. Authenticate against your Chainstack node's per-node URL (e.g. https://nd-XXX-XXX-XXX.p2pify.com/<key>). Merged from the Chainstack Developer Portal per-method fragments at https://github.com/chainstack/dev-portal/tree/main/openapi/arbitrum_node_api.
  contact:
    name: Chainstack API Support
    email: support@chainstack.com
  license:
    name: Chainstack Terms
    url: https://chainstack.com/terms-of-service/
servers:
- url: https://{node_id}.p2pify.com/{api_key}
  description: Chainstack-managed node endpoint
  variables:
    node_id:
      default: nd-000-000-000
      description: Your Chainstack node identifier
    api_key:
      default: <api-key>
      description: Per-node access key
tags:
- name: Events
paths:
  /subscribe_to_events:
    get:
      summary: Subscribe to events
      operationId: subscribeToBeaconEvents
      parameters:
      - name: topics
        in: query
        description: Topics to subscribe to, e.g., 'head'
        required: true
        schema:
          type: string
          default: head
      responses:
        '200':
          description: Successfully subscribed to events
          content:
            text/event-stream:
              schema:
                type: string
                example: 'event: contribution_and_proof

                  data: {"contribution": "...", "proof": "..."}


                  '
        '400':
          description: Invalid request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      tags:
      - Events
components:
  schemas:
    Error:
      type: object
      properties:
        code:
          type: integer
          format: int32
        message:
          type: string
      required:
      - code
      - message