Getting started in the Bluebeam Developer Portal

The Bluebeam API is RESTful and currently has 2 categories of endpoints:

• Authentication

• Studio

Authentication

Some high-level notes of how we handle authentication:

• Authentication with OAuth 2.0

  • All API calls are made under the context of a user. By authenticating with OAuth, a user grants permission to your App to gain access to their data and make API requests on their behalf.

• All requests and response bodies must be JSON formatted. Set the Content-Type: application/json header on all requests that have bodies.

• API calls must be made over HTTPS.

• See our Authentication Guide to start setting up OAuth 2.0 in your App.

Studio

Studio is our cloud collaboration platform with a direct connection to our flagship desktop application: Bluebeam Revu. Our Studio endpoints open up lines of communication for seamless integration between Studio and your systems.

You can generally think about the functionality offered by the Studio API as the same set of functionality that a user would get via the Studio GUI in Revu.

To learn more about Studio, visit our Studio FAQ page.

To speed things up, we recommend using an App called Postman. Here's how:

1. Create a BBID account, if you haven't already.

2. Go to developers.bluebeam.com and log in.

3. Register for access.

   1. Go to My Apps and click Request Access.

   2. Fill out the Request Access form.

   Note for Grant Type:
   Only select the boxes next to:
   • Authorization code
   • Refresh token

   3. Redirect uri: use https://oauth.pstmn.io/v1/callback

   4. Select Request to submit the form.
      

   Approval email
   Upon selecting Request, you'll receive a MuleSoft branded email with the subject: "Application registration approved" – please ignore. It's another unwanted side-effect of using our out-of-the-box solution.
   

4. Get credentials. Now you should see your newly registered App in the list (if you don't see it, refresh your browser). Hover over the key to get your credentials.

   
   

5. Get an access token via Postman.

   1. Access Postman via their desktop app or browser and create a free account.

   2. Here's a script that you can import into Postman. In Postman, go to File > Import, and drop the script in.

   3. To get an access_token in Postman, select the Bluebeam API (Script x.x.x) collection.

   4. Go to the Authorization tab, and replace the orange {{client_id}} and {{client_secret}} variables with the Client Id and Secret that you received in My Apps.

   5. Scroll to the bottom and click Get New Access Token.
      
      

   6. Sign in with your BBID and click Allow Access when prompted. You'll be presented with a token that you can use in Postman, our API docs, or your own code.

Here's a step-by-step process to migrate an existing integration to our new platform.

1. Create a BBID account, if you haven't already.

2. Go to developers.bluebeam.com and log in.

3. Register a new App.

   1. Go to My Apps and select Request Access.

   2. Fill out the Request Access form.

      Note for Grant Type:

      Only select the boxes next to:

      • Authorization code
      • Refresh token

   3. Select Request to submit the form.
      

4. Get credentials. Now you should see your newly registered App in the list. Hover over the key to get your credentials.

   
   

5. Update your existing integration with the new API routes for authorization and Studio endpoints listed below.
   
   

   United States Servers
   Environment	Original Base Route	New Base Route
   Auth – Production (US)	https://authserver.bluebeam.com/auth/oauth/authorize	https://api.bluebeam.com/oauth2/authorize
   Auth – Production (US)	https://authserver.bluebeam.com/auth/token	https://api.bluebeam.com/oauth2/token
   Studio – Production (US)	https://studioapi.bluebeam.com:443/publicapi/v1	https://api.bluebeam.com/publicapi/v1

6. Anywhere you have your legacy Client ID and Client Secret configured in your integration, replace them with your new Client ID and Secret.

7. In your API calls, add a header called "client_id" with the value of your new Client ID. This is required for all requests hitting the new platform.

   Note
   We're still working on making our error messaging more accurate and meaningful, but in the meantime, if you send your request without the "client_id" header, you'll see an error message like this:
   

   Copy

   1
   2
   3
   {
       "msg": "Internal Server Error"
   }

8. Our new platform handles authentication slightly differently from our old platform, so we recommend reviewing our new Authentication Guide . Two noteworthy changes:

   • We've introduced an offline_access scope for refresh tokens (see Step 1 in the Authentication Guide ).

   • Our token endpoint responses have changed (see the Authentication Guide for example responses).

9. If everything is configured correctly, you should receive a response identical to the previous Studio API's response for all Studio endpoints.
   For example, if you requested a list of Studio Projects, your response body would look something like this:
   

   Copy

   1
   2
   3
   4
   5
   6
   7
   8
   9
   10
   11
   12
   13
   14
   15
   {
     "$id": "1"
     "Projects": [
       {
         "$id": "2",
         "Id": "385-509-537",
         "Guid": "Mzu1D6xhLE2bE0y2F4ozfQ",
         "Name": "Test Project Name",
         "Restricted": true,
         "Created": "2024-02-29T17:40:58.043",
         "OwnerNameIdentifier": "e149e277-3052-4f3e-a376-29fc6c5aa76c",
         "OwnerEmail": "jdoe@bluebeam.com"
       }
     ]
   }

10. You did it! Test your app and let us know if you run into any issues.