Skip to main content
A dependency is a scheduling link between two deliverables in the same tree. Creating, changing, or removing one re-rolls the successor’s dates. Standard CRUD applies. See standard endpoints.

​
Fields

Every property the API returns for a dependency. type follows the usual scheduling conventions. fs is the default and covers most real work. lagTimeSec shifts the link. A positive value delays the successor, for example 86400 to hold a phase a day after its predecessor finishes. A negative value leads it.
There is one link per fromId and toId pair. A duplicate comes back as 409.

​
Hierarchy

Return every link in the subtree rooted at an id:
To set a straight sequence under a root, POST /deliverable/reorder is easier than writing links one at a time. It rewrites the dependency chain to match the order you send.

​
What you can write

Everything else in the table above is set by BuildingSwell.

​
Deleting

DELETE /deliverable/dependencies/{id} is destructive.Permanently removes the link. This is not the archive operation and it cannot be undone. The two deliverables stay, and the successor’s dates are re-rolled without the link.
See archiving and deleting for the full picture across resources.