Contact Enrichment API — Append Phones, Emails & Related Persons to CRM Records

What is Contact Enrichment?

Contact enrichment is the process of appending missing or outdated contact information — phone numbers, email addresses, job titles, related persons — to existing records in a CRM, database, or lead list. Instead of manually searching for contact details or buying expensive bulk data subscriptions, you call an enrichment API with the information you already have and receive the missing fields back in the response.

Ava Data's contact enrichment API specializes in person-level data: given a full name and a known address (or city and state), it returns the best current phone number, the best email address, and optionally the related-persons graph. This is PI-grade skip tracing delivered as a developer-friendly JSON API — the same underlying data used by professional investigators and skip trace vendors, available per-match with no subscription lock-in.

Internal links: Skip Tracing API · Phone Number Lookup API · Bulk Skip Tracing · CRM Enrichment glossary · People Search API

What Fields Does the API Return?

The response shape depends on the lookup tier selected:

• Phone only (1 credit / $0.02): phones[] — an array of verified phone numbers ordered by confidence, each tagged with type (mobile, landline, VOIP) and a confidence score.
• Phone + Email (2 credits / $0.04): phones[] + emails[] — the best verified phone and email address for the subject.
• Deep Search (10 credits / $0.20): All of the above plus relatedPersons[] — each related person returned with their name, relationship type, and their own verified phones and emails. Relationships include spouses, domestic partners, siblings, parents, adult children, and known associates.

Every response includes a matchFound boolean, a creditsCharged integer, and a subject object that echoes back the normalized input. If matchFound is false, creditsCharged is 0 and the subject's contact arrays are empty.

Enriching at Scale — Real-Time and Batch

Real-time enrichment is the right pattern when you need to enrich a record the moment it enters your system — a new lead form submission, a CRM record created by a rep, an inbound inquiry that needs a callback number before the first follow-up. Each request takes well under a second and returns JSON that you can write directly to the record.

Batch enrichment handles large backfill jobs — enriching an entire CRM export of 10,000 records, refreshing stale contact data on a prospect database, or appending phones to a real estate list before a campaign. For batch jobs, upload a CSV through the bulk processing endpoint and download the enriched output when the async job completes. Same per-match pricing, no row-based charges.

The two modes use the same underlying data and the same per-match billing. You can mix them freely — real-time lookups for new records, batch jobs for periodic refresh — without managing separate contracts or rate tiers.

Pricing

How to Integrate

Authentication is a bearer token passed in the Authorization header. There is no OAuth flow, no SDK, and no required library — any language that can send an HTTP POST request works.

{
  "firstName": "Robert",
  "lastName": "Chen",
  "address": "1400 Harbor Blvd",
  "city": "Fullerton",
  "state": "CA",
  "returns": ["phone", "email"]
}

{
  "matchFound": true,
  "creditsCharged": 2,
  "subject": {
    "firstName": "Robert",
    "lastName": "Chen",
    "phones": [
      { "number": "+17145550198", "type": "mobile", "confidence": "high" }
    ],
    "emails": [
      { "address": "rchen@example.com", "confidence": "high" }
    ]
  }
}

Full interactive API documentation — including all request parameters, response schemas, error codes, and authentication details — is available inside the app at app.avadata.ai. To request API access, email support@avadata.ai.