# forbidden

> The call isn't allowed

- Status: 403 Forbidden
- Returned by: /api/public
- 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/forbidden
- Try it: `GET https://developers.rivr.io/errors/simulate/forbidden` answers with the code's exact wire form; `?succeedAfter=N&attempt=K` gives a 200 once `attempt` passes `N`

## What it means

The call isn't allowed for the token, for a reason no other code describes. No operation in `/api/public` is documented with the code today; it exists so that an unexpected `403` carries a code too.

## What your system does

Check the token and what the call is about. If it persists, contact Rivr with the call's time and path.

## 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

```http
HTTP/1.1 403 Forbidden
Content-Type: application/json

{
  "propertyName": null,
  "message": "The request is not allowed for the token.",
  "errorCode": "forbidden",
  "code": "forbidden",
  "type": "https://developers.rivr.io/errors/forbidden"
}
```

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