Creates a new policy via a RENEW transaction, linking it to a previous policy. The new policy term must start on or after the previous policy’s end date.
The request body follows the same structure as NEW_BUSINESS — it contains the new policy term dates and the full initial policy state, including policy-level fields, full-term aggregates, and nested exposures. The transaction produces a new policy record with a single segment covering the full renewal term.
Required permission: company.policy:create
API key authentication. Include your API key in the Authorization header.
Company identifier
The ID of the policy being renewed. Must be an existing policy with at least one transaction. The new policy will be linked to this policy.
Renewal term start date in ISO 8601 format. Must be on or after the
previous policy's end date. Must be before newPolicyEndDate.
The day/month/year must match fullTermPolicyInfo.policyStartDate.
Accepts a plain date (2026-01-01) or a full timestamp with UTC offset
(2026-01-01T00:00:00-05:00). Only standard-time (non-DST) offsets are
accepted:
| Timezone | Accepted offset |
|---|---|
America/New_York | -05:00 (EST) |
America/Los_Angeles | -08:00 (PST) |
Daylight-saving offsets (-04:00 EDT, -07:00 PDT) are not accepted.
These are the only two timezones currently supported.
Renewal term end date in ISO 8601 format. Must be after newPolicyStartDate.
The day/month/year must match fullTermPolicyInfo.policyEndDate.
Accepts a plain date (2027-01-01) or a full timestamp with UTC offset.
Only standard-time offsets are accepted — see newPolicyStartDate for the mapping.
Container for renewal policy state. Must contain a policy object with all
policy-level fields and optional nested exposures.
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).
Renewal policy created 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.
Full-term policy information. Contains policy status, term dates, and primary insured reference.
Full-term billing aggregates. Contains premium, taxes, fees, and grand total for the full policy term.