Skip to main content
POST
Reference example

Request contract

  • Method and path: POST /apis/v1/people-data-labs/enrich-person-data
  • Availability: enabled
  • Request URL template: https://api.aisa.one/apis/v1/people-data-labs/enrich-person-data
  • Runtime facts: d9aafd76ae02b9bcd98e168c52eb69aba6e12890a1eed8da421910f394e8200a
Complete OpenAPI definition Effective request and pricing declaration (including authentication and referenced schemas):

Cost and request rules

Usage-based billing; Default request estimate: $0.2803 USD (not a fixed price). Declared unit rate: $0.000001 USD per provider_credit. Account-specific pricing and final settlement may differ. Published reference values are not an account-specific quote or a settled charge. For endpoints supporting X-AISA-Cost-Mode: quote, obtain a free quote for your exact request before execution; reconcile the settled cost with response metadata and Usage Logs. USD amounts use 1,000,000 integer micro-USD per dollar.
  • Default request reference estimate (USD): 0.2803
  • Declared unit rate (USD): 1e-06
  • Billing unit: provider_credit
  • Cost contract: response_units
  • Published reference multiplier: 1.0
  • Declared maximum count/units: 10000000
  • Settlement evidence source: response_body

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
email
string
required

Email address.

Example:

"john.doe@example.com"

lid
string

LinkedIn ID.

Example:

"123456789"

name
string

Full name.

Example:

"John Michael Doe"

phone
string

Phone number; E.164 format recommended.

Example:

"+14155552671"

pdl_id
string

People Data Labs unique record ID.

Example:

"qEnxS5T1G2YvasA1x24qoA_0000"

pretty
boolean
default:true

Format JSON response with indentation for readability.

region
string

State, province, or region of residence.

Example:

"CA"

school
string

School name attended.

Example:

"Stanford University"

company
string

Company name where person has worked.

Example:

"Acme Corporation"

country
string

Country of residence (ISO 3166-1 alpha-2 code or full name).

Examples:

"US"

"United States"

profile
string

Social profile URL (e.g., LinkedIn, Facebook).

Examples:

"https://www.linkedin.com/in/john-doe"

"https://www.facebook.com/jane.doe"

locality
string

City or locality of residence.

Example:

"San Francisco"

location
string

General location (e.g., city, state, country).

Example:

"San Francisco, CA, USA"

required
string

Boolean expression of top-level fields required in enriched profile for match. Use AND/OR operators and parentheses for logic (e.g., 'emails AND phone_numbers', 'education AND (emails OR phone_numbers)'). Valid fields: emails, phone_numbers, experience, education, job_title, job_company_name, full_name, location_country, work_email, personal_emails, mobile_phone, linkedin_url, profiles, skills, etc.

Examples:

"emails AND phone_numbers"

"education AND (emails OR phone_numbers)"

"job_title AND job_company_name"

"experience AND work_email"

last_name
string

Last name.

Example:

"Doe"

birth_date
string

Birth date (YYYY-MM-DD format).

Example:

"1990-01-15"

email_hash
string

SHA-256 or MD5 hash of an email, for matching without exposing the raw email.

Examples:

"d41d8cd98f00b204e9800998ecf8427e"

"e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"

first_name
string

First name.

Example:

"John"

postal_code
string

Postal or ZIP code of residence.

Example:

"94107"

data_include
string

Comma-separated data fields to include in response (e.g., 'emails,phones'). Refer to People Data Labs docs for all fields.

Examples:

"emails,phones,profiles"

"jobs,education"

min_likelihood
integer
default:2

Minimum confidence score (0-10) for a match to be returned; higher is stricter.

Required range: 0 <= x <= 10
Examples:

0

5

10

street_address
string

Street address.

Example:

"123 Main St"

include_if_matched
boolean
default:false

Include input parameters used for matching in the response if true.

Response

Tool result data

data
object
required
status
integer
required
likelihood
integer
required
matched
string[]