Generating LOB-specific endpoints

Cloud API has endpoints that caller applications can use to interact with contents of a policy. In this context, the term "policy" refers to bound policies, unbound policies associated with jobs such as policy changes, and future policies associated with submissions. The Cloud API endpoints can retrieve information about the contents of these policies. Within the context of a job, they can also create and modify the contents of a policy.

The contents of a policy can be divided into two categories:

  • LOB-generic
    • These contents have a structure that remains the same, regardless of the policy's line(s) of business.
    • Examples: policy contacts, policy locations
  • LOB-specific
    • These contents have a structure that varies for each line of business.
    • Examples: coverables, coverages, modifiers

The base configuration contains endpoints for LOB-generic policy contents. But, it does not initially contain endpoints for LOB-specific policy contents. This is because each insurer structures each product to suit the needs of the business. There is no way for PolicyCenter to anticipate in advance how the LOB-specific endpoints need to be structured.

Therefore, in order to work with LOB-specific contents through Cloud API, you must first generate LOB-specific endpoints for each line. This topic describes how to do this.

Note: PolicyCenter provides a mechanism for generating endpoints that let you work with the LOB-specific aspects of policies and jobs. However, this mechanism does not generate or modify the endpoints in the Product Definition API.