Roof measurements in insurance claims workflows

In a claim, the roof measurement is not a sales document. It is the basis of the estimate the carrier pays on, and it has to land in Xactimate under the right claim number without anyone retyping it. This guide is the integration a claims or restoration platform builds on RoofQuery.

How does the claim number get onto the file?

You send it on the order. Pass claim and the technicians put it on the Xactimate file, and the ESX downloads as <claim>.esx, so it lands under the number the adjuster already has open. It is set at order time or not at all, so pass it the moment the claim is created. clientInfo takes the insured's name and contact details and reportName is your own label printed on the report; both are optional. Fields are in the order reference.

What comes back?

• ESX. The measured roof as an Xactimate estimate file. What is an ESX file covers what is in it.
• PDF. The file document, branded as the adjusting firm or the carrier's vendor.
• JSON on the webhook. Squares, pitch areas and edge totals for your own claim record, without opening either file.
• XML. The measurement document, for platforms that generate their own sketch.

What does a claims workflow look like?

1. First notice of loss creates the claim. Your platform orders a report with the claim number and the insured's details.
2. The order is processing, then in-progress. Show it on the claim so the desk adjuster knows a measurement is coming.
3. The completed webhook arrives, typically within two hours for residential. Attach the ESX and PDF to the claim.
4. The adjuster opens the ESX in Xactimate and writes line items on a roof that is already sketched.
5. If the field adjuster disagrees with a measurement, open a revision from the claim. It is free, and the original stays attached while it is redone.

How are supplements and corrections handled?

As redeliveries on the same order: same id, same file URLs, now serving the corrected document. Your platform should re-download on the updated event and keep the prior version itself if the audit trail needs it, because the URLs always serve the current one. The lifecycle reference explains why a corrected report alternates between completed and updated events.

Can the contractor get the file directly?

Yes. The PDF, XML and ESX routes need no API key. A restoration contractor on the claim can be sent the ESX link. The order id is the credential and it does not expire, so treat the link as you would the file.

What does it cost at claims volume?

$13 residential and $35 commercial, drawn from a prepaid balance. There is no subscription, no minimum and no per-seat cost, which suits a claims volume that spikes after a storm and drops in between. Turn on auto-recharge before catastrophe season so a surge never fails on balance.