GET /v1/people/profile: person field reference

GET /v1/people/profile returns a person record: identity, location, network counts, work history, education, skills, badges, verification, and optionally contact details.

Endpoint

GET https://api.triguna.ai/v1/people/profile

curl -H "ApiKey: $TRIGUNA_API_KEY" \
  "https://api.triguna.ai/v1/people/profile?profile_id=rokafor\
&include_network_info=true&include_contact_info=true\
&get_verification_details=true"

Query parameters

The three flags gate whole response sections. Omit them and those objects come back null, which is a common cause of “the API dropped a field” reports.

You can pass a bare slug or a full URL. See identifiers and slugs.

Response headers

Provenance and rate-limit state travel in headers, not in the body:

X-Data-Source: live | store | stale_fallback
X-Fetched-At: 2026-07-31T14:02:11+00:00
X-Data-Age-Seconds: 0
X-RateLimit-Limit: 10
X-RateLimit-Remaining: 9

Full detail in provenance and freshness.

What is not populated yet

Upstream does not expose everything this format can carry. These come back empty today and are back-fillable later, because the raw payload is stored on every call:

Everything else below is mapped and returned: identity, URNs, grouped experience[] with nested positions[], education, skills, all ten generic sections, and contact_info.birth_date.

Top-level fields

Nested objects

{
  "location":     { "name": "Lisbon, Portugal", "city": "Lisbon",
                    "country": "Portugal", "country_code": "PT" },
  "network_info": { "followers_count": 18400, "connections_count": 500,
                    "custom_action": { "url": "https://example.com/",
                                       "label": "Visit my website",
                                       "control_name": "ca_website_view",
                                       "open_externally": true } },
  "badges":       { "premium": true, "creator": true, "influencer": false,
                    "top_voice": false, "open_to_work": false, "is_hiring": true },
  "verifications":{ "is_verified": true, "joined_date": "June 2014",
                    "sections": [{ "title": "Workplace", "items": [] }] }
}

• network_info.custom_action is the optional custom button on the profile.
• verifications.joined_date is a human-readable string such as "June 2014", not an ISO date. Parse accordingly, or store it as text.
• verifications.sections[] has the shape { title, items }, but items was empty in every sample checked.

experience[]

The single most important thing about this endpoint: experience[] is grouped by company, and the job title lives on a nested positions[] array, not on the group. Someone promoted twice at one employer produces one group entry with three positions. Reading experience[0].title returns undefined for effectively every record.

{
  "experience": [
    {
      "company_name": "Northwind Systems",
      "company_id": "1035",
      "company_url": "https://example.com/company/northwind",
      "company_industry": "Software Development",
      "company_employee_count_range": { "start": 101, "end": 500 },
      "workplace_type": null,
      "date_range": {
        "start": { "year": 2023, "month": 11, "day": null, "iso": "2023-11" },
        "end": null
      },
      "positions": [
        {
          "title": "Staff Platform Engineer",
          "description": "Own the retrieval path and its SLOs.",
          "location_name": "Lisbon, PT",
          "employment_type": "Full-time",
          "date_range": {
            "start": { "year": 2025, "month": 4, "day": null, "iso": "2025-04" },
            "end": null
          }
        },
        {
          "title": "Senior Platform Engineer",
          "date_range": {
            "start": { "year": 2023, "month": 11, "day": null, "iso": "2023-11" },
            "end":   { "year": 2025, "month": 4,  "day": null, "iso": "2025-04" }
          }
        }
      ]
    }
  ]
}

Reading the current title correctly:

const currentTitle = record.experience?.[0]?.positions?.[0]?.title ?? null;

• Group fields: company_name, company_id, company_url, company_logo_url, company_industry, company_employee_count_range, workplace_type, date_range, positions[].
• Position fields: everything above except positions, plus title, description, location_name, employment_type.
• Ordering. experience[0] is the current or most recent role, and positions[0] within it is the most recent position.
• Current role. Indicated by an absent or null date_range.end.
• company_id is the reliable identity. Display names drift, so compare company_id when detecting job changes, because comparing names produces false positives.
• There is no company website field on experience[]. Call /companies/details for that.
• company_employee_count_range is an object { start, end }, consistently.
• employment_type observed values: Full-time, Part-time, Contract, Internship, Self-employed, Freelance, Permanent Full-time, and null.
• workplace_type (remote/hybrid/onsite) exists but was unpopulated in every sample checked. Do not build a remote-work filter on it.

Date objects

Dates are objects, not strings, and carry redundant representations:

{ "year": 2018, "month": 3, "day": null, "iso": "2018-03" }

• iso is a partial ISO string such as "2018-03", not a full date. Feeding it to a strict date parser fails.
• day is routinely null and month can be too.
• An absent date_range.end means “present”.
• The company endpoint’s date objects carry no iso key.

education[]

There is no school, institution, or school_logo key. Use school_name and school_logo_url.

skills[]

A plain array of strings, not objects:

{ "skills": ["Distributed Systems", "Go", "Postgres", "Observability"] }

Generic sections

certifications, courses, honors, languages, organizations, patents, projects, publications, test_scores, and volunteer_experiences all share one identical item shape. One parser handles all ten.

languages[] adds one field: proficiency. There are no section-specific keys such as authority, issuer, publisher, role, or cause. Whichever section you read, the shape above is what you get.

contact_info

Only populated when include_contact_info=true.

{
  "contact_info": {
    "email_address": null,
    "websites": [],
    "twitter_handles": [],
    "phone_numbers": [],
    "birth_date": { "year": 1955, "month": 10, "day": 28 },
    "address": null
  }
}