a) API: The Bluebeam Application Program Interface, which includes the programming instructions, standards, protocols, and tools for building Integrations.
b) Bluebeam Technology: The Bluebeam Developer Platform, Bluebeam Revu and Bluebeam Studio or Studio Prime.
d) Developer Platform: The Studio API, API SDKs, scripts, buttons, widgets, app keys, access keys, sandbox environments, developer web pages, and documentation.
f) End User(s): Collective term for all users of both (1) Bluebeam Studio™ and/or Studio Prime™ and (2) Your Integration(s).
g) End User Account: The Bluebeam Studio and Studio Prime account created for an End User.
h) End User Data: All End User specific data, material, content and information obtained by, provided or submitted, to, or through, the Bluebeam Developer Platform or Your Integration, as the case may be, including, without limitation, personally identifiable information, files, activity logs, End User account information, information generated by End User-initiated automated processes and documents uploaded by End Users such as building plan prints, photos, images, cut sheets, and any annotations, notes or other written or electronic additions to those documents.
i) Integration(s): Your Application Software or Integration that utilizes the Developer Platform.
k) Production Access Key: The credentials Your Integration uses to access the Studio API server, allowing Your Integration to be used by End User accounts in production.
l) Sandbox: A Studio Prime environment offered to Developers for the testing of Your Integrations.
m) Studio Platform: Collective term for all Bluebeam products and features that connect to Bluebeam Studio and Studio Prime collaborative cloud environment, including all hosted Studio Projects, Studio Sessions, End User accounts, and the activity therein.
n) Test Access Key: The credentials Your Integration uses to gain access to the Studio API server, allowing You to test Your Integration.
o) Third Party: An individual or entity other than You or Bluebeam.
p) Third Party System: Any additional systems, not created by the Developer or Bluebeam, that are utilized by Your Integration
c) No Access. UPON ANY TERMINATION OR SUSPENSION OF ACCESS TO THE DEVELOPER PLATFORM, YOU MAY LOSE ACCESS TO ANY CONTENT, MATERIALS, OR INFORMATION THAT YOU PROVIDED TO BLUEBEAM THROUGH THE DEVELOPER PLATFORM RELATED TO YOUR INTEGRATION.
- Bluebeam Developer Platform Updates. The Developer Platform will be updated on an ongoing basis as needed at the sole discretion of Bluebeam. Bluebeam will use best efforts to provide advance notice at least five (5) business days prior to a new Bluebeam API release, including detailed release notes of content related to the Bluebeam API, but is under no obligation to do so. All Bluebeam Developer accounts will have access to these changes.
- API Versioning. If Bluebeam deprecates major version releases of the API, the Developer will be notified and will have six (6) months from the date of release to migrate to the new release (“Grace Period”). The Developer will receive notification when a major version has been deprecated. Unless otherwise agreed to in writing by Bluebeam, the Developer will lose access to the deprecated version immediately following the Grace Period.
- Prohibited Actions. You, Your use of the Developer Platform, and Your Bluebeam Developer Integration must not, and must not attempt to: use, display, mirror, frame (including in meta-tags or hidden text), or reverse engineer any Bluebeam Technology, including the Bluebeam API, or any individual element of Bluebeam websites, or the layout and design of any page or form contained on a page, without Bluebeam’s written consent; mislead, confuse, or surprise End Users, or misuse the Developer Platform or help anyone else to do so. For example, Your Bluebeam Developer Integration should be transparent with End Users about what it does – You should get an End User’s consent to (i) modify that End User’s account settings, data, or device, (ii) store or share that End User’s content, or (iii) attempt to gain any rights to that End User’s content.
- Platform Usage
a) Bluebeam may review the Developer Platform (including how our services are being accessed and used), but You acknowledge that Bluebeam has no obligation to do so. Bluebeam is not responsible for files, End User posts on our forums, or any other third party information accessible through the Developer Platform.
b) To protect against malicious activity, Bluebeam may limit the number of calls accepted by services on the Developer Platform if Bluebeam believes that the number of calls may negatively impact the Developer Platform or any other Bluebeam Technology.
- Other Platforms and Users. You are fully responsible for any dealings with (a) the platforms and operating systems on which Your Integration is distributed and used, and (b) the users of Your Integration. Bluebeam has no obligation to provide support to End Users for Your Integrations or Your use of the Developer Platform.
- Endorsements. Unless You have Bluebeam’s written permission, You must not state or imply any endorsement by Bluebeam of Your Integration or other products or services, and You must not make any representations about Your Integration, the Developer Platform, or Bluebeam’s products or services that are false or misleading.
- Technical Support. You are solely responsible for technical support of Your Integrations. Bluebeam will only support product functionality and workflows available without the dependence on Integrations. You will promptly notify Bluebeam of any service issues or complaints You receive from Your End Users regarding Bluebeam products. Bluebeam may use, modify, and incorporate into its products and services and license and sublicense any feedback, comments, or suggestions You provide or post in our forums without any obligation to You. At no time will Bluebeam provide API or development support directly to Your End Users.
- Disclaimer. All functionality introduced by Integrations are Your sole responsibility. Bluebeam is not liable for any Integration, or other developer service that results in a loss of End User Data, unauthorized access to End User Data, or the interruption of End User’s access to Platform Data.
- Trademarks. Please refer to the Bluebeam Developer Network Branding Guidelines for terms relating to use of trademarks and guidelines for naming Integrations.
- Relationship. Bluebeam and You are not legal partners or agents; instead, our relationship is that of independent contractors.