Blockdaemon Documentation

How to Switch from Shared Nodes to Ubiquity

If you are currently accessing blockchains via a Blockdaemon shared node, you will soon be required to switch to our Ubiquity API.

Don’t worry, moving from shared nodes to Ubiquity is incredibly simple.

You only need to change the URL and API Key wherever you access your Endpoints. The URL and API Key structure is explained below:

You can also check out our documentation pages to learn more about Ubiquity.
To learn about native access and the supported protocols, see Ubiquity Native RPC Access API.

Your new Ubiquity URL will take the following format:

https://ubiquity.api.blockdaemon.com/<PROTOCOL>/<NETWORK>/native

You will use this URL together with the specific endpoint and your unique API key.

If you are using the historic Ubiquity URL, please note that it is going to be deprecated soon.

You can use your URL, endpoint, and API Key to connect to Ubiquity in various ways. These include:

Using the auth key as a bearer token in a cURL request, like this:

curl -L -X GET 'https://ubiquity.api.blockdaemon.com/<PROTOCOL>/<NETWORK>/native/<ENDPOINT>' -H 'Authorization: Bearer <YOUR_API_KEY>'

Using your API Key in a URL query parameter, like this:

https://ubiquity.api.blockdaemon.com/<PROTOCOL>/<NETWORK>/native/<ENDPOINT>?apiKey=<YOUR_API_KEY>

For example, if you want to use Ubiquity to list all Stellar Mainnet transactions, you would use the following URL:

https://ubiquity.api.blockdaemon.com/stellar/mainnet/native/transactions

With the auth key as a bearer token in a cURL request, it would look like this:

curl -L -X GET 'https://ubiquity.api.blockdaemon.com/stellar/mainnet/native/transactions' -H 'Authorization: Bearer <YOUR_API_KEY>'

With auth key included in the URL this would be:

https://ubiquity.api.blockdaemon.com/stellar/mainnet/native/transactions?apiKey=<YOUR_API_KEY>