List a subscriber's patients

Method	Path
`GET`	`/v1/signals/api/subscriber/{id}/patients`

The ids of the patients in this tenant the subscriber reads and receives alerts for.

Who can call it: Manager apps, and users whose access policy grants the capabilities.
Capabilities, all required: signals_associations:read. Project admins have every capability; client applications get no admin bypass.
It can reach any patient of your project without naming one, so it is for callers that reach every patient: project admins, manager or submitter apps, and anyone whose Patient access has no criteria.

Request

Name	Type	Required	Description
`id`	string	Yes	The client's `clientId`: the value a patient's `submitters`/`subscribers` hold.

Status	Meaning
`200`	`{ patients: [id] }`.
`400`	A path value holds a character ovok does not send to Signals, such as a raw `:` or `+`. Percent-encode it. The query carries a raw `#`, or more than 200 parameters.
`401`	Your ovok access token, or your client id and secret, are missing or invalid.
`403`	ovok refused the call: you lack a capability this route needs, or your session has no project, or your access covers only some patients. From Signals: Authenticated, but the client's role does not permit this, or it is not attached to the patient.
`409`	Your project has no Signals tenant of its own (`SIGNALS_TENANT_NOT_OWN`), or it is moving to another one.
`429`	Too many requests. Retry after the seconds in `Retry-After`.
`500`	ovok hit an unexpected fault, such as your project having no Signals submitter.
`502`	Signals answered with something ovok couldn't use, or refused ovok's own credential.
`503`	Signals is unavailable. Retry after the seconds in `Retry-After`.
`504`	Signals did not answer in time.

curl --request GET 'https://api.sandbox.ovok.com/v1/signals/api/subscriber/:id/patients' \
  --user "${OVOK_CLIENT_ID}:${OVOK_CLIENT_SECRET}"