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.
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*stringSuccess
application/json- response
data*array<>curl -X GET 'https://api.snoze.dev/v1/workspaces/string/databases/string/gantt/dependencies'{ "data": [ { "id": "string", "workspaceId": "string", "databaseId": "string", "predecessorRecordId": "string", "successorRecordId": "string", "type": "FS", "lagMinutes": 0 } ]}Mint a read-only realtime ticket for a published database
Issues a short-lived, single-use ticket that lets an anonymous reader open a receive-only realtime connection scoped to exactly this published database, so its rows reflect changes without polling. No authentication; the slug is the only credential, and the ticket carries the scope the server resolved rather than anything the caller asked for. Rate limited per client address. A slug that does not exist, is unpublished, or is published in snapshot mode returns the same opaque not-found.
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.