Skip to content

Release Notes

Release notes contain information about new features, improvements, known issues, and bug fixes in each release.

2026-09-04

  • New features:
    • Optional application.drivers[].id and application.vehicles[].id for discount correlation in quote responses. When omitted, positional IDs (d1, v1, …) are assigned by array order.
    • Root-level reports_ran on success and error responses — indicates whether third-party risk-check reports were run for the quote attempt.
    • quote.default_plan_code and quote.payment_plans[] — extensible settlement options (monthly vs paid-in-full, payment method). Existing premium_summary field names are unchanged and always reflect amounts for the default plan.
    • quote.discounts on success responses — policy, driver, and vehicle discount lists (code, name, optional description; no amount).
    • underwriting_messages[] on success responses — underwriting items (code, severity, category, message).
    • marketing_messages[] on success responses — display copy with stable code keys.
  • Improvements:

2026-09-02

  • New features:
    • Agent Validate — POST /account/v1/agent/validate on insurance-api. Validate a rate-partner agent email using the same x-api-key as Partner Quote APIs.

2026-08-25

  • Improvements:
    • Extend Tracking with optional publisher for Consumer Portal publisher attribution.
    • When tracking.publisher is present, or publisher appears as a query parameter on tracking.submission_url, bridge URLs (consumer_bridge_url, agent_bridge_url) include publisher; explicit tracking.publisher wins when both are present.

2026-07-15

  • Improvements:

2026-05-26

  • Improvements:
      • Update paid_in_full_premium form the published PremiumSummary schema to be an optional field.

2026-05-15

  • Improvements:
    • Extend Channel with documented integration_type value zcc.
    • Extend Tracking with optional engagement_id and tracking_number, and add call as a documented traffic_medium value.
    • Extend Pricing with optional bid_id.
  • Documentation:
    • Remove channel_lead_id from the published Channel schema. Pass click partner lead identifiers using Tracking (for example click_id) instead.

2026-05-07

  • Improvements:
    • Extend Tracking to include referral_id and expand traffic_medium to include 'qr_code'.

2025-10-16

  • Improvements:
    • Extend Tracking to include a field for integration click id.

2025-08-12

2025-08-05

2025-07-29

2025-07-11

2025-05-09

2025-05-01

  • Improvements:
    • Extend channel to include a field for click partner lead identifier.

2025-01-08

  • Improvements:
    • Update occupation to an object with both code and description fields.

2024-12-25

2024-11-02

  • First Release