# New guide: Connect a clinic that already has a Rivr account

- Date: 2026-11-10
- Type: New
- Surface: /api/public, Developer portal and CLI
- What you need to do: Nothing.
- Address: https://developers.rivr.io/changelog/2026-11-10-guide-connect-clinic-account

A clinic that already has a Rivr account can now connect it to your platform with OAuth 2.0 authorization code and PKCE: the person signs in at Rivr with BankID, picks the clinic and approves, and you exchange the code for the clinic's id with your own secret. The sandbox first, production when Rivr confirms: the connection is off for every platform until Rivr switches it on. The new guide (/guides/connect-clinic-account) says when to use the connection and when an onboarding link, and covers `GET /oauth/authorize`, the requirements on `state` and PKCE, the code exchange at `POST /oauth/token`, which is form-encoded only, `POST /oauth/deauthorize` and the sandbox's server-to-server approval. `GET /api/public/merchants/{merchantId}` also answers `email`, the clinic's registered contact address. The error codes have a new group for the connection, and a page for `price_list_wrong_market`, which onboarding links have answered with for a while. The page for `price_list_not_allowed` now says that it also comes from `refresh`, and the rate limits have a section for the connection's routes. An integration that doesn't use the connection needs no change.