Get Access

Posts API requires authorized access, you will need to request a client_id and client_secret from our team: [email protected]

Posts API uses an Authorization Header to allow APIs to read and creates Posts for a project*.

This Authorization Header expects your access token that you get by exchanging your client_id and client_secret at the https://bluebeam-atlas-prod.auth0.com/oauth/token endpoint.

*Note: to can create a project at https://atlas.bluebeam.com.

Get your client_id and client_secret from Bluebeam

In order to get a client_id* and client_secret (used to get an access token** to make authorized requests to the Posts API). You will need to reach out to the team.

You can make a request by sending an email to this address: [email protected].

Getting an access token for your API

You can execute a client credentials exchange to get an access token for the Posts API. Here is an example:

cURL

curl --request POST \
  --url https://bluebeam-atlas-prod.auth0.com/oauth/token \
  --header 'content-type: application/json' \
  --data '{"client_id":"YOUR_CLIENT_ID","client_secret":"YOUR_CLIENT_SECRET","audience":"https://atlas.bluebeam-dev.com","grant_type":"client_credentials"}'

Response

JSON

{
  "access_token": "VERY_LONG_ACCESS_TOKEN",
  "expires_in": 86400,
  "token_type": "Bearer"
}

That's it!
Now that the application has an access_token, it is now able to make authorized calls to the API.

Making authorized requests

You can use this bearer token with an Authorization Header in your request to obtain authorized access to your API.

cURL

curl --request GET \
  --url https://atlasapigateway.bluebeam.com/graphql \
  --header 'authorization: Bearer VERY_LONG_ACCESS_TOKEN'