Create a policy on the report. policy_type and policy_status are required.
Coverages may be nested in the request body, together with their own limits, deductibles and premiums, and are created with the policy in the order they appear. Premiums may be nested at the policy level too, and are attached to the policy itself rather than to any of its coverages.
The request is validated in full before anything is written, so a body naming an unknown coverage — or omitting a field something in it cannot be created without — creates nothing at all. If a coverage still cannot be created after that, the policy is removed again, so a failed request leaves nothing behind.
| 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 authenticated client is not permitted to access this resource (e.g. insufficient permissions or org-group scope).
404The specified report was not found.
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.