Environments
Roja runs two hosted environments. Both speak the same API version and are documented by the same API reference.
| Surface | Production | Staging / Development | Purpose |
|---|---|---|---|
| REST API | https://api.getroja.com | https://api.roja.dev | Core backend API (/v1/...). |
| Developer Docs | https://docs.getroja.com | https://docs.roja.dev | Platform documentation and API reference. |
| Customer Web | https://app.getroja.com | https://web.roja.dev | Customer-facing web application. |
| Staff Dashboard | https://staff.getroja.com | https://staff.roja.dev | Operations and underwriting dashboard. |
| Storybook (Web) | None (dev only) | https://storybook.roja.dev | Web/Staff UI component preview. |
| Storybook (Mobile) | None (dev only) | https://storybook-mobile.roja.dev | React Native UI component preview. |
Staging and production are fully separate: accounts, tokens, tickets and loans never cross between them. A staging access token is rejected by production and vice versa.
Versioning
All routes are prefixed with /v1:
https://api.getroja.com/v1/tickets
Backwards-incompatible changes ship as a new version prefix. Additive changes
— new endpoints, new optional fields, new enum values — can appear within
/v1 at any time, so build clients that ignore fields they don't recognize.
Checking connectivity
GET /v1/meta/version is a public endpoint (no authentication) that returns
the running API version — useful as a smoke test for your network setup:
curl https://api.getroja.com/v1/meta/version