Idempotency

Curacel currently documents endpoint-specific idempotency behavior for selected operations.

Confirmed Behavior

The Curacel Health HMO override check-in endpoint documents same-day idempotency. If a check-in already exists for the same enrollee, provider, and day, the existing check-in is returned with HTTP 200 and no new records are created.

This is endpoint-specific behavior, not a general Idempotency-Key contract.

Integration Guidance

Do not assume that every write endpoint is idempotent. Before retrying a write request, check the endpoint documentation and the operation's response behavior.

Curacel does not currently document general REST Idempotency-Key header support across all products. If a future endpoint supports Idempotency-Key, the endpoint documentation and OpenAPI specification should explicitly list the header.