The verified surplus data, as an API.
A clean REST API and webhooks over the same public-record-derived leads you see in the dashboard — the surplus figure, the lien stack behind it, and the recorded documents. Pull it into your own tooling, or have new matches pushed straight into the CRM you already run. We're the data provider; you verify and act.
Dashboard, API, or push — same leads, same evidence.
Dashboard
Browse, filter, open the evidence, export CSV — for when you work leads by hand.
REST API
Self-serve key. Pull leads and their full lien evidence into your own stack.
Push to your CRM
Webhooks and email alerts — GoHighLevel, Zapier, Make, or a raw endpoint.
One key, scoped to your plan.
Create a key in Settings → API keys and send it as a bearer token on every request. A key acts as your account and only returns leads for the states your plan covers — a lead outside your plan reads as 404, exactly like one that doesn't exist.
# pull the feed for one state curl "https://app.surplusledger.com/api/v1/leads?state=AZ" \ -H "Authorization: Bearer sl_live_0123…" # → a filtered, paginated list of leads + headline totals
The figure, and the evidence behind it.
Every lead carries what the surplus figure is (a labeled estimate, never an overstated promise), the lien stack that erodes it, and links to the recorded documents so you can verify at the county.
{
"id": "sl_aZ3f9k2",
"state": "AZ", "county": "Maricopa",
"sale_type": "trustee",
"surplus_estimate": 118400,
"surplus_label": "gross_ceiling", // what the figure represents
"confidence": 0.72,
"liens": [
{ "type": "hoa_assessment", "amount": 9850, "affects_surplus": true }
],
"documents": 3, // recorded-document references
"provenance": "county recorder + trustee sale notice"
}New matches, pushed where you work.
Point a destination at your CRM (or Zapier / Make / a raw endpoint) and every event lands as a signed POST. Filter on the event field in your receiver. The lead payload is exactly what GET /api/v1/leads/{id} returns.
// a new verified lead lands in your system { "event": "lead.created", "at": "2026-11-16T12:00:00.000Z", "lead": { /* the lead object above */ }, "state": { "tracked": false, "dismissed": false } }
| Event | Sent when |
|---|---|
lead.created | a new verified lead matches a state your plan covers |
lead.changed | a published lead's figure, lien stack or status is revised |
lead.tracked | you (or a teammate) Track a lead |
lead.untracked | a tracked lead is un-tracked |
lead.noted | a lead's private note changes |
lead.dismissed | a lead is dismissed |
lead.pushed | you press Push to CRM, or call the push endpoint |
saved_search.matched | a new lead matches one of your saved searches |
X-SL-Timestamp; event + the lead's id + at is always a valid deduplication key. Workspace events get a short retry on transient failures — a slow destination never slows down your own actions.Scoped to how much you pull.
Only successful API-key reads count against the monthly quota — working leads by hand in the dashboard is unlimited within fair use. Webhooks and saved-search matches are push, not metered reads.
| Plan | API reads | API keys | Push destinations | Saved searches |
|---|---|---|---|---|
| Single-State | 2,500 / mo | 2 | 3 | 5 |
| All-Access | 25,000 / mo | 10 | 10 | 25 |
| Firm | 250,000 / mo | Unlimited | 25 | Unlimited |
Limits may change as the product evolves; your dashboard's Settings → API keys page always shows the current quota and usage.
We're the data layer, not another system to live in.
You already have a pipeline. SurplusLedger drops clean, verified, public-record-derived leads into it — figure, lien stack, documents, provenance — so your team verifies at the recorder and acts. We never contact the property owner, and nothing we send is legal advice. That firewall is the whole point: you get information and evidence, and you decide what to do with it.
Do I have to use your dashboard? +
No. The dashboard is one of three co-equal surfaces. Plenty of members never open it — they pull leads through the REST API or have new matches pushed into their own CRM by webhook. Use whichever fits how you already work.
What's in a lead? +
Each lead carries its state, county and sale type, the surplus estimate with the label of what that figure represents, the full lien stack behind it, links to the recorded documents, and the provenance. It's the same data you see in the dashboard — the figure plus the evidence to verify it.
How do I authenticate? +
Create an API key in Settings → API keys and send it as a bearer token on every request. Keys are scoped to your account and only return data for the states your plan covers. A missing, malformed or revoked key returns 401.
Is this a list of homeowners to contact? +
No. SurplusLedger is a data provider, not a recovery service. The API returns public-record-derived facts and evidence so you can verify and act. It never contacts property owners, and nothing in it is legal advice.
What happens if I hit my quota? +
Only successful API-key reads count against your monthly quota — dashboard use is unlimited within fair use. If you exceed it, further API reads return a 429 until the window resets; your dashboard and webhooks keep working. Higher tiers raise the quota.
Get a key and pull your first state.
Subscribe, mint an API key in settings, and the verified feed — figures, lien evidence, recorded documents — is yours to pull or push into your own tools.