Create a timeline dependency between two records
Links a predecessor record to a successor record in the same database; the client may preallocate `id` so an optimistic row and the stored edge share an identity. Requires `databases:write` on the database and a plan that includes the timeline feature. Rejected when either record does not belong to the database, when `lagMinutes` is not a whole number within ten years, when the identical edge already exists, or when the edge would close a cycle.
apiKeyAuthorizationBearer <snoze_sk_…>Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.
workspaceId*stringdatabaseId*stringapplication/json- body
id?|nullpredecessorRecordId*stringsuccessorRecordId*stringtype*string"FS""SS""FF""SF"lagMinutes?number|nullSuccess
application/json- response
data*curl -X POST 'https://api.snoze.dev/v1/workspaces/string/databases/string/gantt/dependencies' \ -H 'Content-Type: application/json' \ -d '{ "predecessorRecordId": "string", "successorRecordId": "string", "type": "FS"}'{ "data": { "id": "string", "workspaceId": "string", "databaseId": "string", "predecessorRecordId": "string", "successorRecordId": "string", "type": "FS", "lagMinutes": 0 }}List the timeline dependencies of a database
Returns every predecessor/successor edge recorded for the database's timeline view, oldest first, each with its dependency `type` (`FS`, `SS`, `FF`, `SF`) and `lagMinutes`. Requires `databases:read` on the database, so a caller without access to it is refused.
Delete a timeline dependency
Removes one dependency edge from the database and records the deletion on the workspace event ledger. Requires `databases:write` on the database; an edge that does not exist in this database returns not-found.