Price a policy

Use this recipe when you need a number, the filing fee, tax, and total cost for a policy, and nothing else. This is the most common thing a partner does with this API.

Just want a price? One call.

POST /partner/calculate is all you need. You do not need to fetch or interpret raw state rates first: /calculate already applies the correct fee engine for the state and returns the finished numbers.

1. Send the inputs

Three fields are required: filingType, stateAbbr, and premium.

Field	Type	Required	Meaning
`filingType`	enum	yes	What kind of transaction this is. See table below.
`stateAbbr`	enum	yes	Two-letter state code, e.g. `WA`.
`premium`	number	yes	The policy premium, in dollars.
`policyFee`	number	no	Policy fee to include in the calculation.
`inspectionFee`	number	no	Inspection fee to include.
`carriersFee`	number	no	Carrier's fee to include.
`lateFee`	number	no	Late fee to include.
`wireFee`	number	no	Wire transfer fee to include.
`lgtValue`	number	no	Override for the state's local government tax value.
`fmtValue`	number	no	Override for the state's fire marshal tax value.

The optional fee fields default when omitted, so a bare filingType + stateAbbr + premium request is a valid, complete quote request.

filingType is one of:

Value	Meaning
`NEW_BUSINESS`	A brand-new policy, filed for the first time.
`NEW_BUSINESS_RENEWAL`	An existing policy being renewed, filed as new business.
`ENDORSEMENT_ADDITIONAL`	A change to an existing policy that adds premium.
`ENDORSEMENT_RETURN`	A change to an existing policy that returns premium (for example a cancellation).

New business vs. endorsement

NEW_BUSINESS and NEW_BUSINESS_RENEWAL are "new business" (NB) filings. ENDORSEMENT_ADDITIONAL and ENDORSEMENT_RETURN are "endorsement" (ED) filings, changes to a policy that's already on file. States sometimes have different requirements or rates for each, which is why the state lookup in State pricing and requirements returns NB and ED fields separately.

cURL

JavaScript

curl -X POST "$BASE_URL/partner/calculate" \
  -H "PartnerKey: $PARTNER_KEY" \
  -H "Content-Type: application/json" \
  -d '{
        "filingType": "NEW_BUSINESS",
        "stateAbbr": "WA",
        "premium": 12500
      }'

const response = await fetch(`${process.env.BASE_URL}/partner/calculate`, {
  method: 'POST',
  headers: {
    PartnerKey: process.env.PARTNER_KEY,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    filingType: 'NEW_BUSINESS',
    stateAbbr: 'WA',
    premium: 12500,
  }),
});

const quote = await response.json();

2. Read the response

{
  "filingFee": 25,
  "tax": 437.5,
  "sFee": 62.5,
  "other": 0,
  "total": 525
}

Field	Meaning
`filingFee`	The state filing fee for this transaction.
`tax`	Surplus lines tax owed on the premium.
`sFee`	Stamping fee (the fee charged by the state's surplus lines stamping office).
`other`	Any other applicable charge (for example local government tax or fire marshal tax, if the state levies one).
`total`	Sum of the above. What the insured owes in taxes and fees for this policy.

That's the full quote. There's nothing else to calculate on your end, add total to the premium if you need the all-in cost to show a client.

No filing has been created yet

/calculate never touches your filing records. It's a pure calculation: same inputs always produce the same outputs, and nothing is saved. When you're ready to actually submit the policy, move on to Submit a filing.

#Price a policy

#1. Send the inputs

#2. Read the response

Price a policy

1. Send the inputs

2. Read the response