# organization_not_accessible

> Organisation not accessible

- Status: 403 Forbidden
- Returned by: /api/public with an organisation key
- Retry (`retryWhen`): `after_fix`
- Did anything happen? (`outcome`): `none` (It did not happen)
- Access and organisation
- Page in the portal: https://developers.rivr.io/errors/organization_not_accessible
- Try it: `GET https://developers.rivr.io/errors/simulate/organization_not_accessible` answers with the code's exact wire form; `?succeedAfter=N&attempt=K` gives a 200 once `attempt` passes `N`

## What it means

The caller doesn't reach the organisation in `Rivr-Organization` at all. On `/api/public`, a missing permission gets `403` with `invalid_scope` instead.

## What your system does

Check the id in the header. If the key should reach that clinic, the clinic needs to be connected to your organisation: contact Rivr.

## Is it worth retrying?

No, not without changing the call.

`retryWhen`: `after_fix`. Change the request first, as the code's page says: a value, the token, a header or a new key. Then send it.

## Did anything happen?

`outcome`: `none`. **It did not happen.** This call did not do what you asked for and changed nothing else that you can see or that concerns money. Where the code has an `outcomeNote`, it takes precedence.

## Example: /api/public with an organisation key

```http
HTTP/1.1 403 Forbidden
Content-Type: application/problem+json
Rivr-Should-Retry: false

{
  "type": "https://developers.rivr.io/errors/organization_not_accessible",
  "title": "The organization API key has no access to that clinic.",
  "status": 403,
  "code": "organization_not_accessible",
  "detail": "The organization API key has no access to that clinic.",
  "instance": "/api/public/orders/7b1e7c3a-2f4d-4a51-9c7e-5d0a6b8e2c14/status",
  "requestId": "5f0c2a7e-9b41-4d3a-8e6f-1c2d3b4a5e6f",
  "retryWhen": "after_fix"
}
```

The `title`, `detail`, `message` and `error_description` texts are exactly as the API writes them today.