Create Override Check-In
POST/v1/enrollees/:enrollee_id/override-check-ins
Confirm an HMO-verified check-in for an enrollee at a provider.
Note: This feature is only available to HMOs/Insurers.
This endpoint is the HMO's own check-in method. Calling it asserts that the HMO has independently confirmed or verified the enrollee through their own channels and is recording that confirmation as a valid check-in for the enrollee at the specified provider.
The resulting check-in is recorded with auth_type = Override, alongside the other verification methods (OTP, facial recognition, fingerprint). Receiving this request is the HMO's confirmation; no further approval step is required. The reason field captures the HMO's verification context for audit.
Same-day idempotency: if a check-in already exists for the (enrollee, provider, today), the existing check-in is returned with HTTP 200 and no new records are created.
This request will succeed when:
- the enrollee belongs to the authenticated Insurer/HMO
- the provider is linked to the authenticated Insurer/HMO
- check-in is enabled for the Insurer/HMO
- the HMO check-in API feature is enabled for the Insurer/HMO
Request
Path Parameters
The ID of the enrollee the override check-in is for.
- application/json
Body
required
The ID of the provider the check-in is being recorded against. The provider must be linked to the authenticated Insurer/HMO.
Possible values: <= 500 characters
Free-text context describing how the HMO verified the enrollee (for example, the verification method used, a reference number, or the staff member that confirmed). Stored on the override record for audit.
Responses
- 200
- 201
- 400
- 401
- 403
- 404
- 422
- 429
An existing same-day check-in was returned. No new records were created.
- application/json
- Schema
- Example (from schema)
Schema
data object
{
"data": {
"check_in_id": 0,
"override_request_id": 0,
"enrollee_id": 0,
"provider_id": 0,
"auth_type": "string",
"confirmed_at": "2026-04-23T14:31:51.437Z"
}
}
The HMO-confirmed check-in was recorded.
- application/json
- Schema
- Example (from schema)
Schema
data object
{
"data": {
"check_in_id": 987654,
"override_request_id": 123,
"enrollee_id": 3298936,
"provider_id": 9568,
"auth_type": "Override",
"confirmed_at": "2026-04-22T14:20:00Z"
}
}
Bad Request (for example, check-in is not enabled for the Insurer/HMO)
Unauthenticated
Forbidden (for example, the HMO check-in API feature is not enabled for the Insurer/HMO)
Not Found (for example, enrollee not found within the authenticated Insurer/HMO scope)
Unprocessable Entity (for example, missing or invalid provider_id or reason)
Too Many Requests