Authentication via a Bearer Token

You can authenticate Ubiquity API requests by setting your API key as a bearer token in the authorization header. Below you will find examples showing how to do it when using cURL and Postman.

Bearer Token in cURL

When working with cURL, use the following code to set your API key as a bearer token:

--header 'Authorization: Bearer YOUR_TOKEN'

For example, to get the current block number in Ethereum Mainnet, run this code:

curl --request GET 'https://stg.ubiquity.api.blockdaemon.com/v1/ethereum/mainnet/sync/block_number' --header 'Authorization: Bearer YOUR_TOKEN'

If you prefer to use short options, run the following:

curl -X GET 'https://stg.ubiquity.api.blockdaemon.com/v1/ethereum/mainnet/sync/block_number' -H 'Authorization: Bearer YOUR_TOKEN'

Bearer Token in Postman

In Postman you can set your API key as a bearer token not only for a particular request but also for a collection of requests.

Go to a request or collection tab and do the following:

1. Navigate to the Authorization or Auth tab
2. Select Bearer Token from the Type drop-down menu
3. Paste your API key into the Token input box

Then you can run your request. For example, to get the current block number in Ethereum Mainnet, use the following:

https://ubiquity.api.blockdaemon.com/v1/ethereum/mainnet/sync/block_number

Getting the Result

If the API key is correct, your request will be authorized, and you will get the result.

The requests from the sections above return the current block number in Ethereum Mainnet, for example:

14589247

If the key is incorrect or missing, you will get the following error:

{
    "status": 401,
    "type": "unauthorized",
    "title": "Invalid Token"
}