Product
Two endpoints. Everything you need about a person or a company.
Triguna turns a LinkedIn profile or company URL into one normalized record, with the origin and age of the data returned alongside it.
Person API
Send a profile slug and receive a person record: identity, location, network counts, work history, education, skills, badges, verification, and optional contact details.
Fields
entity_urnfirst_nameheadlinelocationexperience[]education[]skills[]contact_infosourcefetched_at
Person API → /v1/companies/detailsCompany API
Send a company slug and receive firmographics: identity, headquarters, size, industries, specialities, and the last funding round.
Fields
company_idcompany_namecompany_urllocationsindustries[]specialities[]staff_infofunding_datasourcefetched_at
Company API →What happens on a lookup
A stable shape over data that moves, with every successful lookup stored so a repeat is instant and an outage degrades rather than fails.
-
01
Resolve
A slug, a full LinkedIn URL or a stored entity_urn is resolved to one canonical identifier.
-
02
Fetch
A stored copy under 24 hours old is served instantly, otherwise the record is retrieved live. Either way it is one credit.
-
03
Map
The retrieved payload is mapped into a stable response shape that does not move when the underlying data does.
-
04
Return
JSON on success, with headers giving the source, the age of the fetch and the credit cost.
What Triguna does not do
Being specific about the boundaries is cheaper for both of us than finding them in production.
No search
You resolve identifiers you already have. There is no path that discovers people or companies matching a description.
No bulk endpoint
Enriching N entities costs N calls. Size your budget and your pacing around that from the start.
No claim of correctness
A record says these sources held this value at this moment. That is a narrower claim than truth, and it is one we can actually stand behind.
Start with one request
Free credits on signup, no card required. Usage-based pricing after that.