Developer API · v1

Turn estimate PDFs into Xactimate ESX — over HTTP.

The Antero Trail API takes a carrier estimate PDF and returns a Xactimate-ready .ESX file: rooms, line items, folder hierarchy, and dimensioned measurements, matched against a real Xactimate price list. Upload a PDF, poll or get a webhook, download the ESX.

Base URL

Every endpoint lives under a single versioned base URL:

https://est.anterotrail.com/v1

How a conversion works

Conversions are asynchronous — parsing a PDF and generating an ESX takes real time, so there is no synchronous "give me the ESX now" call. The full round trip is three steps:

Flow

1. POST /v1/conversions           → 202 { job_id, status: "queued" }
2. GET  /v1/conversions/{job_id}  → poll until "succeeded" or "failed"
3. follow esx_url                 → download the .ESX (time-limited link)

Prefer not to poll? Register a webhook and we'll POST the finished job to your endpoint the moment it completes — step 2 disappears entirely.

Quickstart

With a test key, one curl uploads a PDF and starts a conversion. Everything else is polling that job_id until it's done.

curl

curl -s -X POST https://est.anterotrail.com/v1/conversions \
  -H "X-API-Key: at_test_xxxxxxxxxxxxxxxxxxxxxxxx" \
  -F "file=@estimate.pdf;type=application/pdf" \
  -F "price_list=FLTA8X_02MAY26"

202 Accepted

{ "job_id": "b3f1...", "status": "queued" }

From here, poll the job a few seconds at a time. Most conversions finish in under a minute; on success the job carries an esx_url you follow to download the file.

Access

API keys are issued by Antero Trail — there's no self-serve signup. Request access and we'll set you up with a at_test_ key to build against, then a live key when you're ready. Test keys run the identical pipeline but never appear on an invoice.

What's in these docs

Page	What it covers
Authentication	API keys, test vs. live, auth errors.
Conversions	The two core endpoints — start a conversion and read its result.
JSON output	The converted estimate as structured JSON — the `estimate-v1` schema.
Webhooks	Get pushed the finished job instead of polling, and verify the signature.
Errors & limits	Every error code, rate limits, retention, idempotency.
Postman	Ready-to-import collection — set your key and run `GET /v1/ping`.

New

JSON output. Alongside the ESX file, every conversion can now return the estimate as structured JSON — claim header, sections with dimensions, line items with pricing, and notes. Add "json" to output_formats; same single credit either way. See JSON output for the estimate-v1 schema.