---
title: "GetConfigSpec"
method: GET
path: "/{apiKey}/eth/v1/config/spec"
---

# GetConfigSpec

`GET /{apiKey}/eth/v1/config/spec`

Get spec params.

Retrieve specification configuration used on this node.  The configuration should include:
  - Constants for all hard forks known by the beacon node, for example the [phase 0](https://github.com/ethereum/consensus-specs/blob/v1.3.0/specs/phase0/beacon-chain.md#constants) and [altair](https://github.com/ethereum/consensus-specs/blob/v1.3.0/specs/altair/beacon-chain.md#constants) values
  - Presets for all hard forks supplied to the beacon node, for example the [phase 0](https://github.com/ethereum/consensus-specs/blob/v1.3.0/presets/mainnet/phase0.yaml) and [altair](https://github.com/ethereum/consensus-specs/blob/v1.3.0/presets/mainnet/altair.yaml) values
  - Configuration for the beacon node, for example the [mainnet](https://github.com/ethereum/consensus-specs/blob/v1.3.0/configs/mainnet.yaml) values

Values are returned with following format:
  - any value starting with 0x in the spec is returned as a hex string
  - numeric values are returned as a quoted integer

## Path parameters

- `apiKey` string, required — <style> .custom-style { color: #048FF4; } </style> For higher throughput, please <span class="custom-style"><a href="../docs/quick-start-guide#-creating-your-api-key-on-the-zan-platform" target="_blank">create your own API key</a></span>.

## Response `200`

Spec params.

- object
  - `data` object, required — Key value mapping of all constants, presets and configuration values for all known hard forks Values are returned with following format: - any value starting with 0x in the spec is returned as a hex string - numeric values are returned as a quoted integer

---

[API](https://skmtc.net/zan/apis/zan-getnftmetadata.md) · [All operations](https://skmtc.net/zan/apis/zan-getnftmetadata/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/zan/zan-getnftmetadata/versions/be8fa2338895/schema)