Retrieve a node with the Chainstack Platform API
Retrieve configuration, status, and endpoint details for a Chainstack node. Send a GET request to /v1/nodes// using the node’s unique identifier.
Documentation Index
Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
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.
curl -X GET 'https://api.chainstack.com/v1/organization/' \
--header 'Authorization: Bearer FX7CWlLg.FMpAO8cgCX2N7s41EncRru2nb5CmTZUt'All API requests must be made over HTTPS.
Path Parameters
A unique value identifying the Object.
Response
Name of the node.
ID of the network.
ID of the organization that owns this node.
Type of the node.
Available types:
shared— only forethereum,polygon-pos,bsc,avalanche,fantom,tezos,bitcoindedicated— for all protocols
shared, dedicated Cloud provider.
See also Supported cloud providers.
aws, azure, gcloud, vzo Regions the nodes are deployed to.
Available for gcloud:
asia-southeast1
Available for aws:
ap-southeast-1us-west-2us-east-1
Available for azure:
uksouth
Available for vzo:
eu3
asia-southeast1, ap-southeast-1, us-west-2, us-east-1, uksouth, eu3 Protocol-specific attributes.
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
- Option 8
- Option 9
Creator of the network.
When the node was created.
Role of the node.
Available roles:
peer— peer node
peer Ethereum node configuration.
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
- Option 8
- Option 9