Skip to main content

Provider imports

Sink reads environment variables out of Railway, Vercel and Render. The provider token is used for the request that needs it and is never stored.
The whole import route group is gated on a paid entitlement — an unentitled call answers 402.

Discover what a token can reach

provider is railway, vercel or render.
The response lists projects with their environments and services, in the provider’s own vocabulary.

Preview and apply

Base path: /integrations/{workspace_id}/{team_id}/{project_id}/{environment_id}
reveal controls whether preview values come back in clear text or masked. modeskip or overwrite — applies only to the apply call; overwrite records the provider’s value as a new version rather than replacing history. Source shapes per provider, and the CLI equivalent of all of this, are in Import from a provider.

Plans and payments

Subscriptions belong to a user; limits are enforced per workspace against the subscription of the user who owns it. Plans and limits explains the counting rules and what a 402 means.
Creating, editing and delisting plans (POST, PATCH, DELETE on /plans/) is administrative and requires a separate operator token, not an ordinary API key.

CLI distribution

These three are unauthenticated by design — you cannot log in before you have a client. Because the script is served by the deployment it installs a client for, the version always matches the server. The installer verifies the wheel against the manifest before linking sink into ~/.local/bin. A deployment with no published release answers 503 rather than pretending otherwise.

Health

/health answers 200 with "status": "ok", 200 with "degraded" when something non-essential is down, and 503 with "down" when a critical dependency — the database or the master key — is gone. Degraded is deliberately a 200: the node still serves the paths that matter, so a monitor watching the body sees the problem without a load balancer evicting a node that works.