Environments

Three isolated environments, one base URL each — production, staging, and development.

View as Markdown

CloudRaker runs three environments. They are fully isolated: separate data, separate organizations, separate keys. An API key made in one environment does not authenticate in another, and an id from one environment does not resolve in another.

Base URLs

EnvironmentAPI base URL
Productionhttps://api.cloudraker.com
Staginghttps://api.staging.raker.one
Developmenthttps://api.dev.raker.one

Production is also reachable at https://app.cloudraker.com/api — the same gateway, mounted under the web app’s origin. Use it when a browser app needs same-origin calls; use https://api.cloudraker.com everywhere else.

Unless you were given access to staging or development, production is your environment. Staging and development exist for pre-release integration work and carry no availability or data-retention guarantees.

Pointing at an environment

Everything else is identical across environments — same paths, same Authorization: Bearer <token> header, same JSON.

$curl https://api.staging.raker.one/me \
> -H "Authorization: Bearer $RAKERONE_API_KEY"

The API reference and the SDKs default to production.

Where to go next