# Get effective observation ids for a device

Canonical page: https://docs.ovok.com/api/slim/telemetry/get-effective-observation-ids-for-a-device

`GET /v1/slim/telemetry/{deviceId}/effectiveIds`

Returns, for one device, the ids of the Observations that produced its current heart rate, respiratory rate, sleep status and presence values. Use it to trace a displayed value back to its source reading.

**Auth:** bearer token. The caller must be a practitioner, an admin or a System Owner, and needs `Device:read`.
**Scope:** a device identifier only resolves when the device is visible to your token and in the caller's project.

## Behaviour

- `deviceId` is either the device identifier or the Device resource id (a UUID).
- Each field is an Observation id, or `null` when no reading has set that value yet.
- Only devices whose readings carry their own Observation id fill these fields. For other devices every field is `null`.
- A device that is not found returns every field `null`, not an error.
- Lookups of a device are cached for up to 10 minutes, and misses for 30 seconds.

## Example

```bash
curl -X GET 'https://api.sandbox.ovok.com/v1/slim/telemetry/c3499c27-2973-0a7f-807e-fb8676a92dcb/effectiveIds' \
  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE3NjcyNjg4MDAsImV4cCI6MTc2NzI3MjQwMH0.Ql3B_ztDvctlyZ2z0vp4sl3ExXRQGkzmxdmTAqxNzZk'
```
