Headless, if you want it.

Searches, the purpose list and the audit export over REST, for wiring the platform into your own tools.

Authentication

Bearer token in the header. Keys are scoped to an account and revoked one by one.

auth

Authorization: Bearer lds_live_...

Every request needs a purpose

purpose_code is required on every search, with no account-level default. Requests without one are rejected before any source is called.

POST /v1/search

{
  "product":      "person.search",
  "purpose_code": "GLBA_JUDGMENT_ENFORCEMENT",
  "matter_ref":   "24-2-01847-3 KNT",
  "subject": {
    "first_name": "...",
    "last_name":  "...",
    "last_known_address": "...",
    "state": "WA"
  }
}

Response

Every record carries its source. status is hit or no_hit; a no_hit is a search that ran and found nothing.

200 OK

{
  "search_id":  "srch_01JBQ8W2K9",
  "status":     "hit",
  "confidence": "corroborated",   // single | corroborated
  "results": [
    {
      "address":    "...",
      "first_seen": "2023-04",
      "last_seen":  "2026-07",
      "source":     "Credit header"
    }
  ],
  "purpose_code": "GLBA_JUDGMENT_ENFORCEMENT"
}

Errors

Code	Meaning
400	Malformed request or missing `purpose_code`
401	Invalid or revoked key
403	blocked Purpose not permitted for this account or data class
409	The same search ran within the hour; the earlier result is returned by ID
429	Rate limit exceeded
502	Upstream source unavailable
503	No live source for this search yet

A blocked request is still logged, with the reason it was blocked.