Automate Bluebeam Studio Sessions and Projects via the Studio API
domain: developers.bluebeam.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register an app in the Bluebeam Developer Portal to get a Client ID (also used as your Studio integration ID) and Client Secret
Obtain an access token with POST https://authserver.bluebeam.com/auth/token using your client credentials; tokens are valid for 60 minutes
Include the token and a client_id header on every Studio API call, as required by the platform
Use the Sessions group of endpoints to manage real-time markup Studio Sessions, and the Projects group for persistent Studio Project file storage
Use the Jobs group to track long-running asynchronous operations (e.g. bulk file operations) to completion
Known gotchas
Access tokens expire after 60 minutes with no refresh-token grant described in the public docs - plan to re-authenticate rather than assume a refresh flow
Studio Sessions (ephemeral, meeting-like markup) and Studio Projects (persistent file/folder storage) are distinct data models - session endpoints do not work on projects or vice versa
Full endpoint-level request/response schemas are gated behind an approved developer account; publicly indexed pages only describe the three functional groups and the auth flow
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?