Skip to main content
Version: mainnet (v0.74)

Public endpoints

Due to the distributed nature of Vega, most of the APIs are served from a data node, and a few from a core node. This means there is no single API server, and users will need to choose a node to connect to.

This differs from centralised services, as you can't connect to an API server run by a single company, nor does it require a specific access token. When you want to perform an action on the network you'll need to sign the message containing the transaction details with a wallet app or a signer library.

Validators, community members, and other service providers may operate public data nodes. These may have usage restrictions, rate limits, limited data retention, or other restrictions or terms. Check with the individual operator if you have specific needs.

Below, find a list of all the known public servers available for this network, and use them to connect to the API endpoints.

Read more

Data nodes: Find out what a data node is, and if setting one up for yourself is right for you.

Node API endpoints: Mainnet

AddressConnectivitySSL
https://darling.network🔐
https://vega-data.nodes.guru:3008🔐
https://vega-mainnet.anyvalid.com🔐
https://vega.aurora-edge.com🔐
https://vega.mainnet.stakingcabin.com:3008🔐
https://datanode.vega.pathrocknetwork.org🔐
https://graphqlvega.gpvalidator.com🔒
https://rest.velvet.tm.p2p.org🔒
https://vega-data.bharvest.io🔐
https://vega-mainnet-data.commodum.io🔐
https://vega-rest.mainnet.lovali.xyz🔒

Source: github.com/vegaprotocol/networks
Last refreshed: Wed 6 Mar 2024 14:27:27 UTC