Build multi-region integrations

Bluebeam’s API platform supports multi-region integrations through region-specific base URLs, enabling developers and partners to build integrations for customers in hundreds of countries across the globe where Bluebeam is available. Studio data through an integration can be stored in five server regions—United States, Australia, Germany, United Kingdom, and Sweden.

When installing an integration, users select a server region based on their data residency requirements and Studio server region. The integration can then be used globally, as Bluebeam does not enforce geofencing. By leveraging the appropriate region-specific URL alongside your API requirements, you can deliver a consistent integration experience across multiple geographies while maintaining compliance with local infrastructure and data residency standards.

Develop integrations outside of the supported regions (US, AU, DE, UK, and SE)

Integration development through the Bluebeam Developer Portal is available to active customers, channel partners, and software partners in the US, AU, DE, UK, and SE regions. If your organization is outside these regions, select a supported region that best fits your customers' local data residency requirements.

For example, if you are in India, you can build an integration that uses the Australia API endpoints or the US API endpoints, depending on your customers' local data residency requirements.

Customers can choose the server region based on their own project and data residency requirements.
Your Bluebeam subscription’s region determines which API server region you can use. Since Studio Sessions and Projects require a Core, Complete, or Max subscription tied to that region, API calls outside your subscription's region will fail.

To create integrations in two or more server regions, you'll need two or more BBIDs: one per region, each set up with a unique email address and a Core, Complete, or Max subscription assigned to that region.

Select the base URL for your Bluebeam API region

Bluebeam API endpoints remain the same across all regions; only the base URLs differ depending on the selected region.

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

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

Set up multi-region integrations

Each Studio server region operates independently; Sessions and Projects do not transfer across server regions.
Your Bluebeam subscription region, the Studio server region, and the API integration region must match. Otherwise, you'll receive the following error when you try to create an application in a region that doesn't match your Bluebeam subscription region: "No Okta user found.”
Always validate regional data residency and latency requirements for your customers when selecting server regions.

  1. Navigate to the Bluebeam Developer Portal and sign in with your BBID credentials via Okta.

    Your Bluebeam subscription gives you access to the API server region matching your subscription’s region. For example, if your Bluebeam subscription’s region is US, you can create and make calls to the US API region only.

  2. Request Bluebeam API access by region.

    1. In the Developer Portal, go to My Apps and select Create Application.

    2. Use the dropdown menu to select the API instance matching your region when registering.

    3. Complete all required fields:

      • Application Name

      • Description

      • Region

      • Redirect uri: Use https://oauth.pstmn.io/v1/callback.

    4. Select Create Application. Your registered app will be granted access to the region-specific Bluebeam API endpoints.

  3. When integrating, use the appropriate region-specific base URL for each Bluebeam API endpoint.

    For example, the base URL in the US will be https://api.bluebeam.com/publicapi/v1/sessions; the base URL in AU will be https://api.bluebeamstudio.com.au/publicapi/v1/sessions).

  4. For constructing a Bluebeam Studio Session invite URL, use the URL specific to the Bluebeam Studio server:

  5. To create integrations in two or more server regions, you'll need two or more BBIDs: one per region, each set up with a unique email address and a Core, Complete, or Max subscription assigned to that region.

    For example, to create and test an integration in the Australia API region, your Bluebeam subscription and email address must be assigned in the Australia region.

  6. After you create a Bluebeam ID with a Core, Complete, or Max subscription matching the API server region, you can access the Developer Portal with those credentials and create an integration in the matching API region.

Contact Development support

For questions about the integrations functionality, specific API endpoints, and other Bluebeam related questions, email us at integrations@bluebeam.com.

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

Resources

Revu 21

Bluebeam Integrations

Bluebeam Integrations

Bluebeam’s API platform supports multi-region integrations through region-specific base URLs, enabling developers and partners to build integrations for customers in hundreds of countries across the globe where Bluebeam is available.