Add a coverage to a policy. coverage_name, coverage_type and coverage_status are required, and coverage_name must be one enabled for your organization.
Limits, deductibles and premiums may be nested in the request body and are created with the coverage. If any of them cannot be created the coverage is removed again, so a failed request leaves nothing behind.
For an excess layer, send coverage_type: EXCESS with the attachment_point it sits above — Kalepa chains the layers from those attachment points, so the underlying policies are never specified directly.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
400The request is invalid, for example id_type=uuid with a path value that is not a valid UUID, or an id_type other than uuid / external_id.
401The bearer token is missing or invalid.
403The report is within your organization and a visible org group, and you are still not permitted to act on it. A report outside your organization or org group answers 404 instead.
404The report was not found, it belongs to an organization or org group you cannot see, or the addressed policy, coverage, limit, deductible or premium is not part of it. These are reported identically on purpose, so a response cannot be used to discover that a report or a resource exists somewhere you have no access to.
422The request could not be applied, and nothing was created. Either a field the resource cannot be created without was omitted, or the coverage_name is not one enabled for your organization, or that coverage does not allow the coverage_type requested. The response names the field or the coverage.
Every field in these schemas is nullable, so that fields can be added over time without breaking your generated client — which means the schema itself cannot mark anything required. Each endpoint's description states what it needs in order to create.
Also returned when report_id, read as your external_id, matches more than one report (error code AMBIGUOUS_IDENTIFIER, in the response body at detail.code). Narrow with org_group / sub_org_group, or target the report by its Kalepa report ID.
500An unexpected error occurred.