BriteCore provides full, end-to-end policy issuance and management functionality that includes quoting, rating, underwriting, policy generation, and statistical reporting. The entire lifecycle of the policy is managed using convenient interface tools, flexible workflows, and automatic processes that support teamwork and productivity.
Classic Quote provides a dynamic interface for agents and other stakeholders to generate policy estimates based on risk locations, rating details, product lines, and individual carrier risk tolerances. Carriers can configure each screen from collecting contact details, answering initial questions, and completing rating information to submitting an application, evaluating underwriting metrics, and completing final processing.
In this tutorial, we will guide you through creating your own custom quoting application workflow using BriteAPIs for BriteCore Classic.
Processing policy applications through API endpoints in BriteCore occurs in the following broad steps:
- Choose a product for a quote using Effective Date Lookup
- Address lookup to validate addresses
- Create a quote
- Update a quote
- Bind a policy
- Retrieve policy details
- Generate and attach a document
- Get the deliverable list
- Retrieve a specific deliverable
Note: For auto-related quote information, refer to the BriteQuote tutorial.
Key concepts
- Application: The form submitted to an insurer requesting an insurance policy. Applications extend quotes with additional information.
- Bound/Unbound: Binding refers to insurance coverage, and means that coverage is in place, although a policy has yet to be issued. Binding often occurs via verbal agreement, in person, or by phone.
- Coverage: A guarantee of financial restoration for a loss. In BriteCore, coverages are considered a line item under Items.
- Policy: A contract that guarantees insurance coverage for an agreed-upon duration of time.
- Premium: Money paid by a policyholder to an insurance carrier in exchange for insurance.
- Quote: A snapshot of a quoted premium that includes supporting risk and insurance information.
- Quoting: The process of entering risk information, requesting a given level of insurance, and receiving a premium quote for a policy.
- Risk: An asset protected by insurance.
Quote and policy status in BriteCore
The policy status indicates the current state of the policy and appears on each revision. To determine the current status of a policy, view the policy status on the most recent revision.
- Unsubmitted: The quote or application hasn’t been submitted by the agent from the Agent portal.
- Submitted: The application was submitted, but is pending processing by an underwriter.
- Rejected: The application rejected by an underwriter.
- Active: If the revision is committed, the policy and/or endorsement is in effect.
- Cancelled: The policy isn’t in effect.
- Cancellation Pending : The policy is currently in effect, but won’t be as of a future date.
- Expired: The policy was non-renewed and isn’t in effect.
Create and bind a quote using BriteAPIs
Step 1: Get a security token
You will need to request an ID and Secret to use OAuth 2.0.
For more information, refer to How do I get started?
Step 2: Choose a product for a quote using Effective Date Lookup
Use the find_effective_date endpoint to view the list of products available for quoting. You pass the effective date as the starting point. It defaults to the current date.
Sample request
curl --location --request POST '/api/v2/lines/find_effective_date' \
|
Sample response
{
|
Step 3: Address lookup to validate addresses
The retrieveAddressInfo endpoint validates addresses, city and county dropdown lists, and returns geocoding data. You must pass the full address for validation in your request.
Sample request
curl --location --request POST '/api/v2/contacts/retrieveAddressInfo' \
|
‘
Sample response
{
|
Step 4: Create quote
The create_quote_extended endpoint creates and rates a quote by passing in named insured, agency, location, and coverage information.
Sample request
curl --location --request POST '/api/v2/policies/create_quote_extended' \
|
Sample response
{"data": {"contact_info": {"name": "Steve Smith","dob": "08/06/1980","phones": [{"type": "","number": "9785550416"}],"ssn": "989155578","type": "individual","emails": [{"type": "","email": "smith.steven@email.com"}],"addresses": [{"address_line2": "","address_city": "Boston","address_line1": "123 Main St","type": "Mailing","address_county": "Suffolk","address_state": "MA","address_country": "USA","address_zip": "02110"}]},"policy_number": "Q-2020-67"},"messages": ["Named insured info does not have required fields."],"success": false} |
Step 5: Update quote
Use the requote_extended endpoint to update an existing quote’s information, including named insured, agency, location, and coverage Information. You will need the policy_number from Step 4.
Sample request
curl --location --request POST '.com/api/v2/policies/requote_extended' \
|
Sample response
{
|
Step 6: Bind policy
Use the bind endpoint to bind a quote and issue a policy. This endpoint generates declarations and creates a billing schedule.
Sample request
curl --location --request POST '/api/v2/policies/bind' \
|
Sample response
{
|
Step 7: Retrieve policy details
The retrieve_policy endpoint retrieves bound policy details—policy terms, coverage details, billing schedule and payments, related people and organizations (named insured, agent, mortgagee, inspector), and filed claims.
Sample request
curl --location --request POST '/api/v2/policies/retrieve_policy' \
|
Sample response
{
|
Step 8: Generate and attach a document
The create_deliverable endpoint generates a specified deliverable type and stores it in the Attachments module. S3 file paths are returned, the last part of the response is the File GUID.
Sample request
curl --location --request POST '/api/v1/deliverables/create_deliverable' \
|
Sample response
{
|
Step 9: Retrieve the deliverable list
The list_attachments endpoint retrieves all the deliverables (attachments) listed under the policy or contact. policy_id is required.
Sample request
curl --location --request POST 'https:///api/v2/deliverables/list_attachments' \
|
Sample response
{
|
Step 10: Retrieve a specific deliverable
Use the get_attachment endpoint to retrieve a specific deliverable.
Note: The endpoint returns a Base64 encoded payload of your PDF. You need the
file_idfor the attachment.
Sample request
curl --location --request POST 'https:///api/v2/deliverables/get_attachment' \
|
Sample response
{
|
You have successfully created and bound a quote.