Bluebeam Integrations Hub

Since third-party integrations are developed by integration partners or developers, some may have specific requirements such as compatible application versions or additional costs. If you have questions about installing or upgrading to the latest version of an integration, please reach out directly to the integration partner or developer for assistance.

If you use Studio Prime for integrations, you'll no longer need Prime to enable a supported integration. The integrations platform creates a seamless experience that enables you to access connected applications.

If you use Studio Prime for Studio user management, you can continue to use Prime until December 31, 2025. Org Admin will have new user management capabilities that will be available to you in Q3 2025. We encourage you to migrate to our new Studio user management solution in Org Admin once it becomes available. See more details here.

Existing integration partners are migrating to the new platform. The final deadline to migrate is June 30, 2025. New integration partners are building their apps on the new platform. You should work directly with the software partners who developed the integration to install or upgrade to their latest version.

We provide links to our partner websites in the Bluebeam Integrations Directory. You do not have to take any action on your Bluebeam account to use integrations via the new platform.

Bluebeam customers who use integrations should work directly with the integrations partners to install or upgrade to the latest version of their integration as needed. You do not need to update anything within Bluebeam to use the integrations besides having an active subscription.

Yes! A big part of moving to the new platform is to enable our customers to use SSO/SCIM when using integrations, a capability that was not possible with Prime. This will help some users complete their transition to subscription.

The required subscription for using integrations depends on the specific use case for your integration. To create Studio Sessions via an integration, you must have a Core or Complete subscription. To only view Studio Sessions to collaborate via an integration, you only need a Basic subscription.

Currently, the new Integrations platform supports users of Revu 20 and Revu 21 to access Studio Sessions or Projects created through an integration. At this time, Revu 20 users should not experience any interruptions. Please note that this support policy may change in the future. If any changes are planned, we will notify Revu 20 users in advance.

The Bluebeam Developer Portal, for integrations development, is only available to active customers, channel partners, and software partners in the US, AU, and DE regions. If you are based outside these regions, please select one of the regions above based on your local data residency requirements and potential data latency considerations.

There are region-specific base URLs that apply to all endpoints:

- US: https://api.bluebeam.com

- DE: https://api.bluebeamstudio.de

- AU: https://api.bluebeamstudio.com.au

For example, https://api.bluebeam.com/publicapi/v1/sessions in the US would be https://api.bluebeamstudio.com.au/publicapi/v1/sessions in AU.

A 404 bad request error may be caused by a token issue. This can happen if another user account without Developer Portal access was automatically selected on the login screen. The incorrect token then prevents you from logging in successfully. To resolve this, ensure you are logging in with the correct account that has Developer Portal access.

We also suggest trying the following troubleshooting steps to resolve the 404 bad request error:

- Try accessing the Developer Portal in an incognito window or a different browser to log in with the credentials for the Developer Portal.

- Clear your browser cache and try logging in with the credentials for the Developer Portal.

If the steps above do not resolve the issue, the problem may be related to single sign-on (SSO) authentication. If your domain uses SSO with an authenticator such as Okta Workforce, it can cause a configuration conflict that results in a 404 bad request error. To fix this, make sure to add the Developer Portal to your licensing group. This will resolve the issue and allow proper access.

1. You must include offline_access as a scope when generating your access token.

2. For the refresh token requests, you only need the refresh_token and grant_type fields in the body. It will fail if you add anything more.

3. Format the Authorization header as follows:
Authorization Basic {base64 encoded string of client_id:client_secret}

For detailed information on API endpoints and the latest updates to the Integrations platform, visit the API Docs section in the Developer Portal.