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.

Bluebeam customers who use integrations should work directly with the integrations partner 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 Bluebeam plan.

We provide links to our integrations partners' websites in the Bluebeam Integrations Directory.

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 a Bluebeam plan.

Third-party integrations can be used without a Studio Prime or Org Admin Pro subscription.

To create Studio Sessions and Projects through an integration, you must have a Bluebeam Core, Complete, or Max plan.

To attend and collaborate in Studio Sessions and Projects through an integration, you must have at least a Bluebeam Basics plan.

If you are a Revu 20 user, you can attend and collaborate in Studio Sessions and Projects through an integration; you cannot create them via the Bluebeam Studio API.

To create Studio Sessions and Projects through an integration, you must upgrade to a Bluebeam Core, Complete, or Max plan.

The Bluebeam Developer Portal, for integrations development, is only available to active customers, channel partners, and software partners in the US, AU, DE, UK, and SE 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

- UK: https://api.bluebeamstudio.co.uk

- SE: https://api.bluebeamstudio.se

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.