Read files, folders, and ToDos from a Trimble Connect project via the Core API
domain: developer.trimble.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate per Trimble Identity OAuth2 and obtain an access token scoped to Trimble Connect
Use the Core API's standard REST verbs (GET/PUT/POST/DELETE) against the correct regional endpoint for the project, since regions are isolated from each other
List project files/folders and download file content through the Core API's file resources
List and create ToDos, which can carry tags, object links (attachments, linked model objects, clashes), and saved 2D/3D views
For model-specific queries (federated model objects, property sets), use the companion Model API and Property Set API rather than the Core API alone
Known gotchas
Resources in one Trimble Connect region are not visible from another region's endpoint - a project's data lives in exactly one region
The Core API, Model API, Model Feature API, and Topics (BCF) API are separate, independently documented surfaces - a ToDo's linked view is not the same object as a Topics/BCF viewpoint
Trimble's docs site renders via client-side JS and some deep links redirect to a canonical OpenAPI reference path - bookmark the OpenAPI reference rather than a specific guide URL
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?