# merchant_token_required

> The token isn't issued for a clinic

- Status: 401 Unauthorized
- Returned by: /api/public
- Operations: [createOrder](https://developers.rivr.io/reference/api-public/createOrder.md), [getDevices](https://developers.rivr.io/reference/api-public/getDevices.md), [listOrderSettlements](https://developers.rivr.io/reference/api-public/listOrderSettlements.md), [getOrderSettlement](https://developers.rivr.io/reference/api-public/getOrderSettlement.md), [getNextUnreadSettlement](https://developers.rivr.io/reference/api-public/getNextUnreadSettlement.md), [createSubscription](https://developers.rivr.io/reference/api-public/createSubscription.md), [getSubscription](https://developers.rivr.io/reference/api-public/getSubscription.md)
- 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/merchant_token_required
- Try it: `GET https://developers.rivr.io/errors/simulate/merchant_token_required` answers with the code's exact wire form; `?succeedAfter=N&attempt=K` gives a 200 once `attempt` passes `N`

## What it means

The operation is about one clinic, and the clinic is read from the token. The token isn't issued for a clinic, for example a platform token. Nothing was read or changed.

## What your system does

Call with the clinic's token: a token fetched with the clinic's client credentials, or the organisation key's token with the clinic in `Rivr-Organization`. The same token gets the same answer again.

## 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 401 Unauthorized
Content-Type: application/json

{
  "propertyName": null,
  "message": "The token is not issued for a merchant. Use a token issued for the merchant the request is about.",
  "errorCode": "merchant_token_required",
  "code": "merchant_token_required",
  "type": "https://developers.rivr.io/errors/merchant_token_required"
}
```

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