API Updates - Release 7.3

Edited

Status: Live
Effective as of: 03/06/2025


This article summarizes the recent updates to Advocate Technologies' REST API. These changes have now been implemented, and the official API documentation has been updated accordingly.

Policy Version

  • A new attribute, perilsByAsset, has been added. This attribute displays perils on a policy, segmented by assets, to accommodate different peril selections for different assets within a policy. The existing perils attribute has been removed.

  • A new attribute, policyStructure, has been introduced to denote the structure of a given policy. The exact ENUM values have been documented and include:

    • standaloneProperty

    • standaloneLiability

    • trueScheduled

    • trueBlanket

    • scheduledBlanket

    • multiLocationLiability

Policy

  • The attributes perils, perilsByAsset, and policyStructure have undergone the same changes on Policy as they did on Policy Version (as outlined above).

  • A new policy creation endpoint has been introduced, allowing REST clients to create policies. The exact attributes that can be passed are now detailed in the updated documentation.

  • When creating a policy via the REST API, it must be for a post-close loan and basic renewal. The perilsByAsset applicable to the policy defaults to "unknown," meaning REST clients only need to send an array of relevant assets without specifying perils.

  • To create a policy, REST clients must now pass a productType, and a new endpoint has been provided for this purpose.

Product Type

  • A new GET endpoint has been introduced, allowing REST API clients to fetch all product types or retrieve a specific product type by ID. This endpoint should be used to provide the appropriate productType when creating a policy.

These updates are now fully implemented. If you have any questions or need further assistance, please refer to the updated API documentation or contact our support team.