Contact Data

Every person field we hold, its fill rate, and whether the API returns it by default or on request.

Every contact the Signal API returns carries one consistent person profile. The same profile appears on contact enrich, contact search, and on any signal that is about a person.

This page lists every person field we hold, in two tables:

Coverage

AttributeValue
Person profiles in the Autobound identity graph1B+ globally (about 30% US)
Profiles served by contact enrich616M
Signal-linked contacts with full enrichment17.1M
Lookup keyscontact_email, contact_linkedin_url
Stable IDid (UUID). The same person returns the same id on every endpoint.
RefreshMonthly identity build. Signals update daily.
DeliveryREST API, MCP, flat file (GCS)

Standard fields

These fields come back in every API response that includes the contact. No extra setup.

Fill is the share of the 17.1M signal-linked contacts that have a value (October 2026). When we have no value, the API leaves the key out. Treat a missing key as unknown.

FieldGroupDescriptionFill
idIdentityAutobound person ID (UUID). Stable across endpoints and refreshes.100%
first_nameIdentityFirst name98.9%
last_nameIdentityLast name98.9%
full_nameIdentityFirst and last name98.9%
linkedin_urlIdentityLinkedIn profile URL100%
headlineIdentityLinkedIn headline, for example "VP Marketing at Example Corp"67.0%
cityLocationCity84.5%
stateLocationState or region82.0%
countryLocationISO 3166-1 alpha-2 country code90.0%
job_titleCurrent jobCurrent job title97.2%
seniorityCurrent jobStaff, Manager, Director, VP or CXO86.6%
departmentCurrent jobOne of 18 departments (see Values)80.6%
current_jobCurrent jobObject: company_name, company_domain, company_id, title, seniority, department, as_of. company_id joins to the company object.96.7%
emailEmailThe address you sent on enrich, or the email on the signal—
emails[]EmailEvery known address: address, type (business or personal), status, last_verified. Business addresses are verified (valid). Personal addresses return unknown.91.0%
work_history[]Careercompany_name, company_domain, company_id, title, start_date, end_date, is_current71.5%
education[]Careerschool, degree, field_of_study, start_year, end_year64.3%
skills[]CareerSelf-reported skills60.6%

Available on request

We can add any of these fields to your API responses, or deliver them as a monthly flat file to your GCS bucket, under a data agreement. Send the fields and record volume to [email protected]. We send back a sample with your own records matched.

Fill is the share of the source dataset that has a value (October 2026):

  • US: our US person dataset (287M records).
  • B2B: our US B2B person dataset (122M records).
FieldGroupDescriptionFill
mobile_phonePhoneMobile number55.1% US
direct_numberPhoneDirect business or personal landline42.0% US
personal_phonePhonePersonal landline42.0% US
company_phonePhoneMain number of the person's company29.1% US
business_emailEmailPrimary business email, with business_email_validation_status (Valid ESP, Valid Digital, Valid Catch-All) and business_email_last_seen29.5% US
programmatic_business_emailsEmailLikely business addresses built from the name and the company email pattern29.6% US
personal_emailsEmailPrimary personal email62.2% US
additional_personal_emailsEmailOther personal emails18.8% US
personal_emails_validation_statusEmailValidation status of the personal email, with personal_emails_last_seen48.2% US
personal_addressHome addressStreet address, plus personal_address_272.2% US
personal_city, personal_stateHome addressHome city and state75.2% US
personal_zipHome address5-digit ZIP74.6% US
personal_zip4Home addressZIP+4 extension62.5% US
dpv_codeHome addressUSPS delivery-point confirmation: Y confirmed, D primary only, S secondary unconfirmed, N failed48.9% US
professional_addressWork addressOffice street, city, state, ZIP and ZIP+4 for the person (can differ from company HQ)14.3% US
genderDemographicsM, F, U98.1% US
age_rangeDemographics18-24 to 65 and older61.5% US
marriedDemographicsY, N40.7% US
childrenDemographicsY, N28.9% US
income_rangeDemographicsUnder $20K to $250K+41.7% US
net_worthDemographicsUnder $0 to over $1M47.2% US
homeownerDemographicsY, N, P (probable)40.0% US
job_title_normalizedJob detailTitle with standard elements ("CEO" becomes "Chief Executive Officer")32.7% US
job_title_last_updatedJob detailDate the title last changed22.2% US
job_start_dateJob detailStart date in the current role67.2% B2B
recent_job_changeJob detailFlag for a recent move75.8% B2B
compensation_estimateJob detailModeled annual salary84.6% B2B
social_connectionsSocialLinkedIn connection band: 1-9, 10-49, 50-99, 100-249, 250-499, 500+25.3% US
hashed_emailsIdentity linkageSHA-256, SHA-1 and MD5 of lowercased emails, for match-back and audience onboarding1.76B hashes
ip_to_hashed_emailIdentity linkageIP address to hashed-email links, for website visitor identification287M IPs
International profilesInternational766M non-US business profiles (top: IN, BR, GB, CN, FR, CA, MX): LinkedIn, job title, business email, company, city, work history, education. No phones or demographics.LinkedIn 96.0%, title 38.4%, business email 16.7%

Where the contact object appears

EndpointWhat you getCredits
POST /v1/contacts/enrichThe profile once at the top, plus every signal for that person2 per signal returned. 1 when the person has no signals (profile only, profile_only: true).
POST /v1/contacts/searchOne record per contact with the profile and its top signals2 per contact returned
Any signal with association: "contact"The contact object on that signalBilled with the parent call

To check an email address in real time, use POST /v1/emails/verify (1 credit per email; unknown results are free).

Example

POST /v1/contacts/enrich with {"contact_linkedin_url": "https://www.linkedin.com/in/jane-doe-example"} returns:

{
  "contact": {
    "id": "5df7542a-0000-4000-8000-000000000001",
    "first_name": "Jane",
    "last_name": "Doe",
    "full_name": "Jane Doe",
    "headline": "VP Marketing at Example Corp",
    "linkedin_url": "https://www.linkedin.com/in/jane-doe-example",
    "job_title": "VP Marketing",
    "seniority": "VP",
    "department": "Marketing",
    "city": "Boston",
    "state": "MA",
    "country": "US",
    "current_job": {
      "company_name": "Example Corp",
      "company_domain": "example.com",
      "company_id": "3365d9b9-0000-4000-8000-000000000002",
      "title": "VP Marketing",
      "seniority": "VP",
      "department": "Marketing",
      "as_of": "2026-09-01"
    },
    "work_history": [
      {
        "company_name": "Example Corp",
        "company_domain": "example.com",
        "title": "VP Marketing",
        "start_date": "2023-04-01",
        "is_current": true
      },
      {
        "company_name": "Prior Co",
        "title": "Director of Demand Generation",
        "start_date": "2019-02-01",
        "end_date": "2023-04-01",
        "is_current": false
      }
    ],
    "education": [
      {
        "school": "Boston University",
        "degree": "Bachelor",
        "start_year": 2008,
        "end_year": 2012
      }
    ],
    "skills": [
      "Demand Generation",
      "B2B Marketing",
      "Marketing Automation"
    ],
    "emails": [
      {
        "address": "[email protected]",
        "type": "business",
        "status": "valid",
        "last_verified": "2026-09-30"
      }
    ]
  }
}

The full response also carries the company object (see Company Data) and the contact_signals array.

Values

Seniority (5): Staff, Manager, Director, VP, CXO. Filters accept common synonyms ("C-Suite", "Vice President", "Head of").

Department (18): Administrative, Community And Social Services, Education, Engineering, Executive, Finance, Government, Health Services, Human Resources, Information Technology, Legal, Marketing, Media And Communications, Military And Protective Services, Operations, Product Management, Real Estate, Sales.

GET /v1/filters returns the current lists for free.

Compliance

  • Opted-out persons return no profile fields on any endpoint.
  • Consumer attributes (home address, personal email, demographics) are US-only and licensed for marketing and identity-resolution use. They are not consumer reports and may not be used for credit, employment, insurance or tenant screening decisions (FCRA).
  • Contact [email protected] for data-subject requests.

Migrating from the flat-file schema

Earlier versions of this page described a flat file keyed on up_id and cc_id. The API now keys every person on id and every company on company_id. The buyer-intent contact endpoints still return up_id for backward compatibility.


Did this page help you?