Delete Coverage¶

Removes an insurance plan from a patient.

Endpoint¶

DELETE /v2/patients/{patient_id}/coverages/{coverage_id}

Path Parameters¶

Parameter	Type	Required	Description
`patient_id`	string	Yes	The patient. Correlate on this — it's a stable id, and there's no external-reference field.
`coverage_id`	string	Yes	One of the patient's coverages, from `GET /v2/patients/{patient_id}/coverages`.

Request¶

curl --location '{base_url}/v2/patients/63120/coverages/90455' \
  --request DELETE \
  --header 'Authorization: Bearer JWT_TOKEN'

Response¶

Success Response¶

Code: 204 No Content

No response body.

Error Response¶

Code: 400 Bad Request

{
  "code": "bad_request",
  "message": "Validation failed",
  "errors": [
    {
      "field": "patient_id",
      "message": "must be a string"
    }
  ]
}

Every error has the same shape — a machine-readable code, a message, and an errors[] array that's empty when there's nothing field-specific to report. The HTTP status is authoritative.

Status	`code`	Meaning
`400 Bad Request`	`bad_request`	The request body or parameters failed validation. `errors[]` names the offending fields.
`401 Unauthorized`	`unauthorized`	The access token is missing, malformed or expired.
`403 Forbidden`	`forbidden`	The request references a resource outside the token's organisation or clinic scope.
`404 Not Found`	`not_found`	No such resource, or it's outside your scope.
`429 Too Many Requests`	`rate_limited`	Rate limit exceeded. Back off and retry.
`500 Internal Server Error`	`internal_error`	Unexpected server error.
`502 Bad Gateway`	`upstream_error`	Upstream service failed or timed out.