tc_object_links
Link entities such as todos, files, and views to model objects in Trimble Connect. Supports listing, creating in bulk, updating, and deleting object links.
Instructions
Trimble Connect Object Links (link entities like todos/files/views to model objects). Select the endpoint with the "action" parameter. Path placeholders {projectId}/{id}/{subId}/{extraId}/{version} are filled from the matching input parameters. Actions:
list: GET /objectlink — query: {projectId, objectId?...}
list_for_target: GET /objectlink/target — query: target entity params
create: POST /objectlink — body: object link
bulk_create: POST /objectlink/objectlinks — body: array of object links
update: PATCH /objectlink/{id} — id=linkId, body: fields to update
delete: DELETE /objectlink/{id} — id=linkId
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Primary resource ID — required when the action path contains {id} | |
| body | No | JSON request body for POST/PUT/PATCH (and some DELETE) actions | |
| query | No | Query parameters as key-value pairs | |
| subId | No | Secondary resource ID — required when the action path contains {subId} | |
| action | Yes | Endpoint to call (see tool description) | |
| region | Yes | Trimble Connect region: us (North America), eu (Europe), ap (Asia-Pacific), ap-au (Australia) | |
| extraId | No | Tertiary resource ID — required when the action path contains {extraId} | |
| version | No | Version number — required when the action path contains {version} | |
| projectId | No | Project ID — required when the action path contains {projectId} | |
| bcfVersion | No | BCF API version for BCF actions (default 2.1) |