Full skip-trace dossier for a known person_id

POST /api/properties/skip-tracing/person-details/

1 credit

What it returns

Full skip-trace dossier for a single person — current and previous addresses, phone numbers (with type and connectivity status), email addresses (with verification status), relatives, and associates. The person_id input must come from a prior call to skip-tracing/associated-people — this endpoint does not accept free-form name lookup.

When to use it

Pricing

1 credit per call. A first call for a given person_id hits the upstream provider; subsequent calls within the per-user history cache are free. Identical calls from other accounts hit a shared global cache but still cost 1 credit (the data has value; the speed is the gift).

Errors

StatusMeaning
400Missing person_id field, or person_id not recognized by the provider.
401Authentication failed.
402Insufficient credits.
502Upstream skip-tracing microservice unavailable. Safe to retry with exponential backoff.

FAQ

How fresh is the data?

The upstream provider refreshes records on its own cadence; we don't control it. For privacy-sensitive use cases, treat addresses older than 12 months as stale.

What's the difference between this and skip-tracing/associated-people?

associated-people returns a list of people tied to a property address with minimal detail per person (name, relationship inference, person_id). This endpoint takes one of those person_ids and returns the full dossier for that one person. Use them together: list → drill down.

Why might current_addresses be empty?

The provider has no current-address record for the person. This is common for transient or recently deceased individuals.

Is the data court-admissible?

No. Skip-trace data is research-grade aggregation of public records and is not certified for legal proceedings.

Responses

More in Skip Tracing