Documentation
Triguna API documentation
Two authenticated GET endpoints are the whole integration. Start with the
quickstart, then read the reference for the endpoint you are
calling.
Documentation
Introduction
Triguna turns a profile URL or a company URL into one structured record, assembled from independent sources at request time, with source and fetched_at on every record.
Quickstart
Get a Triguna API key, make an authenticated GET request to the person and company endpoints, and read the record that comes back. Two requests, start to finish.
Authentication
Triguna authenticates with a custom ApiKey request header. How key scoping, test versus live keys, credit ceilings, rotation, and idempotency keys work in practice.
Provenance and freshness
Every Triguna response carries where the record came from and how old it is, in headers rather than in the body. How to read them and how to control freshness.
Identifiers and slugs
Triguna accepts a LinkedIn slug, a numeric company id, or a full profile URL and extracts the identifier for you. Which keys are safe to store, and what still fails.
API reference
Person profile
Every field the Triguna person endpoint returns: identity, location, network info, experience, education, skills, generic sections, and contact info, with parsing notes.
Company details
Every field the Triguna company endpoint returns: identity, locations, size, industries, specialities, URLs, flags, and funding, with the traps that catch parsers.
Conventions and errors
Triguna status codes, plain-text error bodies, Retry-After handling, the rate-limit headers, and what each failure means for your credits.
Ready to make the first call?
A test key returns shaped sample records and never spends credits.