Reinstate Policy Transaction
Reinstates a previously cancelled policy as of a given date via a REINSTATE transaction. The policy must be cancelled at the reinstatement date.
reinstatementDate (= the transaction effective date) is sugar the server expands into
per-segment, segment-scoped deltas. policyStatus flips back to active from the
reinstatement date through end of term, and cancellationEffectiveOnDate is cleared
across the whole term — reinstatement removes the cancellation marker rather than recording
a parallel reinstatement marker. There is no reinstatement date field.
A reinstate may not leave a coverage gap. A reinstate that would leave a cancelled
window between two active periods (e.g. cancel Jun 15, reinstate Jul 1, leaving
Jun 15–Jun 30 cancelled) is rejected with a 400 — the domain models that as a new policy
term, not a reinstatement. A valid reinstate restores continuous coverage and fully clears
the cancellation, so the segments return to their pre-cancellation state (and merge).
Two optional derived channels are whole-object overwrites of a policy-root full-term container — necessarily whole-term, so neither carries dates nor an element-level form:
fullTermPolicyBillingInfo— full-term billing (e.g. reinstatement fees). ItspolicyPremiummust equal the pre-cancel premium. WhenfullTermPolicyBillingInfois omitted, the cancelled policy’s current full-term billing carries forward and that carried-forwardpolicyPremiumis validated against the pre-cancel premium — so a barereinstatementDatebody only succeeds when the carried-forward premium already equals the pre-cancel premium (a cancel that wrote a reduced short-rate premium leaves a carried-forward premium that will be rejected).fullTermPolicyRatingResult— the canonical policy-level rating result.
Required permission: policy:update
Authorizations
API key authentication. Send your raw API key as the Authorization header value with NO scheme prefix — Authorization: YOUR-API-KEY. Do NOT prefix it with Bearer or ApiKey, and do not use an X-API-Key header; those are not accepted.
Path Parameters
Company identifier
Policy identifier
Body
The date the reinstatement takes effect in ISO 8601 format. Must fall within the policy term, and the policy must be cancelled at this date.
When the business decision was made. Defaults to the current time if omitted. Set explicitly for imports (e.g., aligning to a bordereau booking date).
Optional whole-object overwrite of the policy-root full-term billing summary
(e.g. reinstatement fees). policyPremium must equal the pre-cancel premium;
fees, taxes, and grand total may be adjusted.
Optional whole-object overwrite of the policy-root canonical rating result.
Response
Policy reinstated successfully
Response returned by policy transaction endpoints. Contains the policy version produced by the transaction, including all derived segments.
Policy identifier
Sequential version number produced by this transaction
Identifier of the transaction that produced this version
Policy term start date (ISO 8601)
Policy term end date (ISO 8601)
When the transaction was created (ISO 8601)
Derived segments for this policy version. Each segment represents a maximal contiguous date range where policy state is identical. Adjacent segments with identical data are automatically merged.
Endorsable full-term policy info, hoisted as a read-once convenience (also
duplicated in every segment). Contains term dates, the renewal pointer
(previousPolicyId), and the primary insured reference. Term bounds are
sourced here. Segment-scoped policyStatus is not part of this object.
Derived full-term billing aggregates, hoisted as a read-once convenience (also duplicated in every segment). Contains premium, taxes, fees, and grand total for the full policy term.
Derived canonical policy-level rating result for the full term, hoisted as a
read-once convenience (also duplicated in every segment). Element-level rating
output (crossSegmentRatingOutputs) stays inline at its host and is not hoisted.
