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.
Query Parameters
Which field to use when ordering the results.
Use the - prefix to perform descending ordering (-name).
name, created_at A page number within the paginated result set.
Filter by project ID.
Filter by organization ID.
Filter by network ID.
Filter by the region the node is deployed to.
asia-southeast1, ap-southeast-1, us-west-2, us-east-1, uksouth, eu3 Filter by the cloud provider of the node.
aws, azure, gcloud, vzo Filter by protocol.
ethereum, polygon-pos, bsc, avalanche, arbitrum, near, aurora, gnosis, cronos, fantom, starknet, harmony, tezos, fuse, bitcoin Filter by node status.
pending, running, maintenance, failed, error, stopping, stopped, starting Filter by node role.
peer Filter by node type.
shared, dedicated Filter Ethereum, Polygon PoS, Binance Smart Chain, Avalanche, Fantom, and Tezos nodes by the archive mode flag.
Filter by public network.
ethereum-mainnet, ethereum-ropsten-testnet, ethereum-rinkeby-testnet, polygon-pos-mainnet, polygon-pos-testnet, bsc-mainnet, bsc-testnet, avalanche-mainnet, avalanche-testnet, arbitrum-mainnet, arbitrum-goerli, near-mainnet, near-testnet, aurora-mainnet, aurora-testnet, gnosis-mainnet, gnosis-testnet, cronos-mainnet, cronos-testnet, fantom-mainnet, fantom-testnet, starknet-mainnet, starknet-testnet, harmony-mainnet, harmony-devnet, tezos-mainnet, tezos-testnet, fuse-mainnet, fuse-testnet, bitcoin-mainnet, bitcoin-testnet "corda-network-uat"
Filter by name.
Filter by project type.
public