# A guide to which key you need

- Date: 2026-11-01
- Type: New
- Surface: Developer portal and CLI
- What you need to do: Nothing.
- Address: https://developers.rivr.io/changelog/2026-11-01-guide-which-key

The new guide Which key do I need? (/guides/which-key) tells the platform client and the organisation key apart. It says who creates each, where each fetches its token (the platform client as JSON from `auth.test.rivr.io`, the key form-encoded from `auth.test.rivr.tech`, where `resource` is required), which calls need which (the list of clinics and onboarding only the platform client, order calls either), which `public:*` scopes each capability gives a key, why `customers:read` is health data and `orders:read` is enough to confirm a payment, and which error code points to the wrong key: `merchant_token_required`, `platform_token_required`, `route_not_available`, `invalid_scope` and `organization_required`.