Links an existing item to more objects; a target it is on already is left as it is
Confirms that a link marked CHECK on the version is on the right object
Which objects of a version have linked data: for colouring and markers
Optionaloptions: { includeLater?: boolean }The item's content, as uploaded: a file byte for byte, a URL, identifier or text as text/plain
A URL of the item's content, valid for a few minutes without a token (treat it like the file itself), that supports Range, for a browser tab, a player or a PDF viewer. With inline: true it shows the content when the type allows it; disposition says what it will do.
Optionaloptions: { inline?: boolean }Ends a link from the version on; the older versions keep it
One item, its links with their trail across versions, and its replacements
OptionalversionUuid: stringLinks every item to every target; a refused item does not refuse the others
Optionaloptions: LinkedDataProgressOptionsThe linked data on a version, followed up to it first
Optionaloptions: ListLinkedDataOptionsWhat this server accepts: the file families, the deny list, the limits, the categories
Puts a link on another object from the version on
Deletes items from every object and version, restorable for the policy's retention_days
Optionalreason: stringReplaces an item from a version on; the older versions keep it
Optionaloptions: LinkedDataProgressOptionsTakes links off their objects on every version; an item that loses its last link is deleted
Edits what can be edited; a stale rowVersion rejects with VERSION_CONFLICT
Files, URLs, texts and identifiers linked to objects, which follow their objects to later versions. Available through BimWorksClient.linkedData. Reading needs the scope
links:read, changinglinks:write.