Skip to main content
POST
Create node

Authorizations

Authorization
string
header
required

Chainstack API uses API keys to authenticate requests. You can view and manage your API keys in the platform UI. Your API keys carry many privileges, so be sure to keep them secure! Provide your API key as the Authorization header. The value of the header consists of Bearer prefix and secret key generated through the platform UI.

All API requests must be made over HTTPS.

Body

application/json
name
string
required

Name of the node.

project
string
required

ID of the project.

Example:

"PR-123-123"

cloud
string
required

ID of the cloud.

Example:

"CC-0016"

blockchain
string
required

Blockchain identifier.

Example:

"BC-000-000"

Response

id
string
required
read-only
name
string
required

Name of the node.

network
string
required
read-only

Network identifier from the platform catalog, for example ethereum-mainnet.

protocol
string
required
read-only

Protocol name.

project
string
required

ID of the project.

cloud
string
required

ID of the cloud.

region
string
required
read-only

Cloud region.

provider
string
required
read-only

Cloud provider.

status
string
required
read-only

Status of the node.

details
object
required
read-only

Protocol-specific attributes: https_endpoint, wss_endpoint, and api_namespaces, plus, depending on the protocol, fields such as beacon_endpoint, graphql_endpoint, grpc_endpoint, and grpc_x_token. Dedicated nodes can also return metrics_endpoint — see Dedicated node monitoring.
Endpoint URLs include the node's auth token, and grpc_x_token is the token itself — treat them as secrets.

blockchain
string
required

Blockchain identifier.

Example:

"BC-000-000"

Last modified on May 4, 2026