Rivet Cloud control-plane HTTP API

REST discovered

Details

URL: https://api.rivet.dev
Docs: https://rivet.dev/actors/docs/debugging/

Authentication

Rivet secret token (`sk_`) bearer discovered Get token ↗

Authorization: Bearer <credential> /Authorization: URL userinfo in endpoint, e.g. https://<namespace>:sk_xxxxx@api.rivet.dev <credential>

Mint a namespace or deployment secret token from the Rivet dashboard, then use it server-side only. Rivet docs show secret tokens with the sk_ prefix and recommend them for private control-plane access and debugging. You can supply it separately as RIVET_TOKEN with RIVET_NAMESPACE, or embed it in the endpoint URL like https://<namespace>:sk_xxxxx@api.rivet.dev. The CLI can also persist credentials after rivet deploy --token <token>.

Rivet Cloud token bearer discovered Get token ↗

Authorization: Bearer <credential>

In the Rivet dashboard, go to Settings > Advanced > Cloud Token in dashboard.rivet.dev and issue a cloud token. Keep it server-side. The Dynamic Apps docs say deployApp() uses RIVET_CLOUD_TOKEN to create each app namespace through the Rivet Cloud API.