> ## Documentation Index
> Fetch the complete documentation index at: https://docs.validationcloud.io/llms.txt
> Use this file to discover all available pages before exploring further.

# /eth/v1/beacon/genesis

> Retrieve details of the chain's genesis.

<CodeGroup>
  ```bash title="Mainnet" theme={"theme":{"light":"github-light","dark":"github-dark-default"}}
  curl -X GET \
      "https://mainnet.ethereum.validationcloud.io/v1/<YOUR_API_KEY_HERE>/eth/v1/beacon/genesis" \
      -H "Content-Type: application/json" 
  ```

  ```bash title="Testnet" theme={"theme":{"light":"github-light","dark":"github-dark-default"}}
  curl -X GET \
      "https://sepolia.ethereum.validationcloud.io/v1/<YOUR_API_KEY_HERE>/eth/v1/beacon/genesis" \
      -H "Content-Type: application/json" 
  ```
</CodeGroup>


## OpenAPI

````yaml nodeapi/openapi/beacon-node-oapi-v2.json GET /eth/v1/beacon/genesis
openapi: 3.0.3
info:
  title: Eth Beacon Node API
  description: >
    API specification for the beacon node, which enables users to query and
    participate in Ethereum 2.0 phase 0 beacon chain.


    All requests by default send and receive JSON, and as such should have
    either or both of the "Content-Type: application/json"

    and "Accept: application/json" headers.  In addition, some requests can
    return data in the SSZ format.  To indicate that SSZ

    data is required in response to a request the header "Accept:
    application/octet-stream" should be sent.  Note that only a subset

    of requests can respond with data in SSZ format; these are noted in each
    individual request.


    API endpoints are individually versioned.  As such, there is no direct
    relationship between all v1 endpoints, all v2 endpoints,

    _etc._ and no such relationship should be inferred.  All JSON responses
    return the requested data under a `data` key in the top

    level of their response.  Additional metadata may or may not be present in
    other keys at the top level of the response, dependent

    on the endpoint.  The rules that require an increase in version number are
    as follows:

      - no field that is listed in an endpoint shall be removed without an increase in the version number
      - no field that is listed in an endpoint shall be altered in terms of format (_e.g._ from a string to an array) without an
        increase in the version number

    Note that it is possible for a field to be added to an endpoint's data or
    metadata without an increase in the version number.
  version: v2.3.0 - Eth2Spec v1.1.0
  contact:
    name: Ethereum Github
    url: https://github.com/ethereum/beacon-apis/issues
  license:
    name: CC0-1.0
    url: https://creativecommons.org/publicdomain/zero/1.0/
servers:
  - url: https://mainnet.ethereum.validationcloud.io/v1/<YOUR_API_KEY_HERE>/
    description: Mainnet Beacon API
  - url: https://sepolia.ethereum.validationcloud.io/v1/<YOUR_API_KEY_HERE>/
    description: Sepolia Beacon API
security: []
tags:
  - name: Beacon
    description: Set of endpoints to query beacon chain.
  - name: Config
    description: Endpoints to query chain configuration, specification, and fork schedules.
  - name: Debug
    description: Set of endpoints to debug chain and shouldn't be exposed publicly.
  - name: Events
    description: Set of endpoints to for event subscription.
  - name: Node
    description: Endpoints to query node related informations
  - name: Validator
    description: Endpoints intended for validator clients
  - name: ValidatorRequiredApi
    description: >
      Minimal set of endpoints to enable a working validator implementation.


      [Checkout validator
      flow](https://github.com/ethereum/beacon-APIs/blob/master/validator-flow.md)
      to learn how to use this api.
paths:
  /eth/v1/beacon/genesis:
    get:
      tags:
        - Beacon
        - ValidatorRequiredApi
      summary: Retrieve details of the chain's genesis.
      description: >-
        Retrieve details of the chain's genesis which can be used to identify
        chain.
      operationId: getGenesis
      responses:
        '200':
          description: Request successful
          content:
            application/json:
              schema:
                type: object
                title: GetGenesisResponse
                properties:
                  data:
                    type: object
                    properties:
                      genesis_time:
                        allOf:
                          - type: string
                            example: '1'
                          - example: '1590832934'
                          - description: >-
                              The genesis_time configured for the beacon node,
                              which is the unix time in seconds at which the
                              Eth2.0 chain began.
                      genesis_validators_root:
                        type: string
                        example: >-
                          0xcf8e0d4e9587369b2301d0790347320302cc0943d5a1884560367e8208d920f2
                        pattern: ^0x[a-fA-F0-9]{64}$
                      genesis_fork_version:
                        type: string
                        description: a fork version number
                        example: '0x00000000'
                        pattern: ^0x[a-fA-F0-9]{8}$
        '404':
          description: Chain genesis info is not yet known
          content:
            application/json:
              schema:
                allOf:
                  - type: object
                    properties:
                      code:
                        description: >-
                          Either specific error code in case of invalid request
                          or http status code
                        type: number
                        example: 404
                      message:
                        description: Message describing error
                        type: string
                      stacktraces:
                        description: Optional stacktraces, sent when node is in debug mode
                        type: array
                        items:
                          type: string
                  - example:
                      code: 404
                      message: Chain genesis info is not yet known
        '500':
          description: Beacon node internal error.
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    description: >-
                      Either specific error code in case of invalid request or
                      http status code
                    type: number
                    example: 404
                  message:
                    description: Message describing error
                    type: string
                  stacktraces:
                    description: Optional stacktraces, sent when node is in debug mode
                    type: array
                    items:
                      type: string
              example:
                code: 500
                message: Internal server error

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.