# Record an eligibility check

Canonical page: https://docs.ovok.com/api/patient-billing/record-an-eligibility-check

`POST /v1/patient-billing/coverages/{coverageId}/eligibility-checks`

Records a check that the coverage is in force, as the clinic ran it, such as the health card's online check in its practice software: a FHIR `CoverageEligibilityRequest` and the insurer's `CoverageEligibilityResponse`. Ovok does not reach the insurer itself.

**Scope:** the caller's project, with `PATIENT_BILLING_ENABLED` on.

## Behaviour

- Your access policy must grant `patient_billing_claims` `create` and let you read the patient, else **403** `PATIENT_BILLING_NOT_ALLOWED`. A coverage you cannot see answers **404** `COVERAGE_NOT_FOUND`.
- A self-pay coverage has no insurer: **422** `COVERAGE_NOT_INSURED`. `clinicId` must be a clinic the patient is enrolled with, else **422** `BILLING_CLINIC_INVALID`.
- `inForce` is what the insurer answered; `outcome: error` records a check that failed. Answers **201** with `Location: /v1/patient-billing/eligibility-checks/<id>`.
- `identifier` is optional. With it, the same identifier for the same patient again answers the check already recorded, with **200**.

## Example

```bash
curl -X POST 'https://api.sandbox.ovok.com/v1/patient-billing/coverages/<coverageId>/eligibility-checks' \
  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE3NjcyNjg4MDAsImV4cCI6MTc2NzI3MjQwMH0.Ql3B_ztDvctlyZ2z0vp4sl3ExXRQGkzmxdmTAqxNzZk' \
  -H 'Content-Type: application/json' \
  -d '{ "clinicId": "<clinicId>", "servicedOn": "2026-11-18", "outcome": "complete", "inForce": true }'
```
