# subscription_not_found

> Subscription not found

- Status: 404 Not Found
- Returned by: /api/public
- Operations: [getSubscription](https://developers.rivr.io/reference/api-public/getSubscription.md)
- Retry (`retryWhen`): `after_fix`
- Did anything happen? (`outcome`): `not_applicable` (No side effect)
- The request
- Page in the portal: https://developers.rivr.io/errors/subscription_not_found
- Try it: `GET https://developers.rivr.io/errors/simulate/subscription_not_found` answers with the code's exact wire form; `?succeedAfter=N&attempt=K` gives a 200 once `attempt` passes `N`

## What it means

There is no subscription with the id that the token reaches. A subscription of a clinic on another platform gets the same answer. The body used to be the framework's ProblemDetails without a code.

## What your system does

Check the id, and that the call is made with the token for the clinic that owns the subscription.

## 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`: `not_applicable`. **No side effect.** The call has no side effect, since it is a read.

## Example: /api/public

```http
HTTP/1.1 404 Not Found
Content-Type: application/json

{
  "propertyName": "subscriptionId",
  "message": "The subscription was not found",
  "errorCode": "subscription_not_found",
  "code": "subscription_not_found",
  "type": "https://developers.rivr.io/errors/subscription_not_found"
}
```

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