Endpoint · Profiles

Get a profile

One person: names, current role, work history and contact emails.

GET/v1/profiles/{profileReference}

Authentication

Bearer token in the Authorization header. The token reaches what your plan covers. Getting a token.

Parameters

path parameters

profileReferenceuuid·pathrequired
The person's reference.

Response

success holds the object below.

  • referenceuuid
  • namesobject{ fullName, firstName, lastName }.
  • current_roleobject | nullThe latest role: { title, organisation, start_date }.
  • confidenceScorenumber | null
  • experiencesarrayWork history, one entry per role.Show 6 fields
    • referenceuuid
    • organisationobject | null{ reference, name }.
    • occupation_titlestringThe title as recorded.
    • occupationobject | null{ reference, name }, the normalised job title.
    • startDatedate | null
    • endDatedate | nullNull on a current role.
  • emailsarray{ value, domain, confidence_score, is_valid } per address.
  • linksobject | array{ Linkedin: { href } } where known.

A profile can carry more fields than are listed here. Treat unlisted fields as unstable.

Examples

Set CHIKARA_API_TOKEN and each sample runs as written. Example records are invented.

curl -sS "https://api.chikaraintel.com/v1/profiles/a1b2c3d4-e5f6-4a7b-9c8d-e9f0a1b2c341" \
  -H "Authorization: Bearer $CHIKARA_API_TOKEN" \
  -H "Accept: application/json"

See pagination and errors.

Used by

MCP tools built on this endpoint.

Related