Preview what deleting a data source would affect
Returns the dependency impact report for the data source, separating blocking dependents from warnings. Requires read access to the data source. Use it before `delete` to decide whether the confirmation flag is needed.
apiKeyAuthorizationBearer <snoze_sk_…>Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.
workspaceId*stringdataSourceId*stringSuccess
application/json- response
data*curl -X GET 'https://api.snoze.dev/v1/workspaces/string/data-sources/string/deletion-impact'{ "data": { "target": { "kind": "workspace_item", "id": "string", "label": "string" }, "status": "safe", "summary": { "blockers": 0, "warnings": 0, "cascades": 0 }, "entries": [ { "id": "string", "kind": "workspace_item", "level": "blocking", "label": "string", "reason": "string", "action": "string", "remediation": { "capability": "actions.delete", "args": { "actionId": "string" } }, "owner": { "id": "string", "kind": "string", "label": "string" } } ] }}Delete a data source
Removes the data source, its run history, and its workspace item while leaving the synced database and its records in place, after checking the deletion impact. Requires `data_sources:write` and edit access to the data source's item; when the impact carries warnings the call is rejected until it is repeated with `confirmed=true`. Send an `Idempotency-Key` header to make retries safe; a replay within the window returns the original response.
Run a data source sync now
Claims the data source and runs a sync immediately outside its schedule, returning the resulting run record. Requires `data_sources:write` and edit access to the data source's item. A disabled source, or one refreshed moments ago and not in an error state, is rejected as a validation error by the manual-run cooldown. Send an `Idempotency-Key` header to make retries safe; a replay within the window returns the original response.