# device_not_found

> No such device at the clinic

- Status: 400 Bad Request
- Returned by: /api/public
- Operations: [sendOrderToDevice](https://developers.rivr.io/reference/api-public/sendOrderToDevice.md)
- Retry (`retryWhen`): `after_fix`
- Did anything happen? (`outcome`): `none` (It did not happen)
- Sending an order to a device in /api/public
- Page in the portal: https://developers.rivr.io/errors/device_not_found
- Try it: `GET https://developers.rivr.io/errors/simulate/device_not_found` answers with the code's exact wire form; `?succeedAfter=N&attempt=K` gives a 200 once `attempt` passes `N`

## What it means

No device with `deviceId` is registered to the clinic that owns the order. An unknown device and another clinic's device get the same answer. The status is 400, as before.

## What your system does

Pick a device from `GET /api/public/devices` for the clinic.

## 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 400 Bad Request
Content-Type: application/json

{
  "propertyName": "DeviceId",
  "message": "No device with the given deviceId is registered to the merchant",
  "errorCode": "device_not_found",
  "code": "device_not_found",
  "type": "https://developers.rivr.io/errors/device_not_found"
}
```

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