Skip to main content
POST
Reference example

Request contract

  • Method and path: POST /apis/v1/people-data-labs/identify-person-data
  • Availability: enabled
  • Request URL template: https://api.aisa.one/apis/v1/people-data-labs/identify-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.5503 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.5503
  • 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

An email address associated with the person.

Example:

"john.doe@example.com"

lid
string

The person's LinkedIn ID. This is a numerical ID found in some LinkedIn URLs.

Example:

"123456789"

name
string

The full name of the person.

Example:

"John Michael Doe"

phone
string

A phone number associated with the person.

Examples:

"+14155552671"

"415-555-0110"

pretty
boolean
default:false

If true, the JSON response is pretty-printed for easier human readability.

Examples:

true

false

region
string

The state, province, or region where the person resides or has resided.

Examples:

"CA"

"New York"

school
string

The name of an educational institution the person attended.

Examples:

"University of California, Berkeley"

"Stanford University"

company
string

The name of a company where the person is or was employed.

Examples:

"Acme Corp"

"Globex Corporation"

profile
string

A social media profile URL associated with the person, e.g., a LinkedIn or Twitter profile URL.

Examples:

"https://www.linkedin.com/in/johndoe"

"https://twitter.com/janedoe"

locality
string

The city or locality where the person resides or has resided.

Examples:

"San Francisco"

"New York"

location
string

A general location query (e.g., 'San Francisco, CA', 'London, UK') associated with the person.

Examples:

"San Francisco, CA"

"London"

last_name
string

The last name of the person.

Example:

"Doe"

titlecase
boolean
default:false

If true, returns all text values in title case (e.g., 'John Doe'). Otherwise, text is returned as is.

Examples:

true

false

email_hash
string

An MD5 or SHA-256 hash of the person's email address.

Examples:

"55502f40dc8b7c769880b10874abc9d0"

"8b21e5e33be1739a3eda69c1046d1385022b8817999b5a76e9300dd839cb2569"

first_name
string

The first name of the person.

Example:

"John"

postal_code
string

The postal or ZIP code where the person resides or has resided.

Examples:

"94107"

"10001"

street_address
string

The street address where the person resides or has resided.

Example:

"123 Main St, Anytown, USA"

include_if_matched
boolean
default:false

If true, the response will include a 'matched_on' attribute, an array of strings indicating which input parameters led to the match.

Examples:

true

false

Response

Tool result data

status
integer
required
matches
object[]