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

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.

Below, find a list of all the public endpoints available for this network.

Node API endpoints

NameAddressConnectivity
greenfield-one.mainnethttp://greenfield-one.mainnet.vega.community:3009
vega.xprv.iohttp://vega.xprv.io/datanode
mainnet.vega.blockscope.nethttp://mainnet.vega.blockscope.net:3009
rest.velvet.tm.p2p.orghttps://rest.velvet.tm.p2p.org:443
restvega.gpvalidator.comhttp://restvega.gpvalidator.com:3009
rockaway.mainnethttp://rockaway.mainnet.vega.community:3009
vega-data.nodes.guruhttp://vega-data.nodes.guru:3009
vega-mainnet-data-rest.commodum.iohttps://vega-mainnet-data-rest.commodum.io
vega-mainnet.anyvalid.comhttp://vega-mainnet.anyvalid.com:3003
vega-rest.bharvest.iohttps://vega-rest.bharvest.io
vega-rest.mainnet.lovali.xyzhttps://vega-rest.mainnet.lovali.xyz
vega.mainnet.stakingcabin.comhttp://vega.mainnet.stakingcabin.com:3009

Source: github.com/vegaprotocol/networks
Last refreshed: Wed 15 Mar 2023 15:59:50 UTC