Real-time professional-identity and job-posting graph over a REST API

Real-time professional-identity and job-posting graph over a REST API: job postings with status through closed/expired, postedAt, salary, workplace and employment type, experience level, per-posting applicant counts and apply URLs, plus endpoints that resolve a posting to its named hiring team (managers and recruiters with profiles) and postings back to individual professional profiles. Job data is one facet of a 200+ attribute identity graph spanning people, companies, emails and domains, each field carrying its source and last-refreshed timestamp.

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Linkdapi and files the sample in your catalog — private to you.

Start 7-day trialNothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry: Human Capital & Employment Services
Instruments: equities
Categories: AlternativeReference

Dataset card

Type: not stated
Format: Tabular — JSON over REST, credit-metered per request (1 credit per search, details, company-jobs or hiring-team call), sub-200ms responses, with playground and dashboard access
Volume: Marketed as 'millions of job listings' plus a 'large-scale identity graph' at 200+ attributes per resolved profile; no exact record count is published for either the postings set or the profile graph, so treat 'millions of postings' as the vendor's own bound and unverified.
Users: Not disclosed — self-serve developer API with 100 free credits on signup and non-expiring credits; no customer count or logos published. The motion (free signup plus a custom-quote enterprise tier) implies low thousands of registered developer accounts with far fewer paying.
History: 0 years
Update frequency: not stated
Growth: Active with an identity reset — LinkdAPI rebranded to Renidly in 2026 with a new site, new product-line architecture and a no-subscription/24-7-support go-to-market; endpoints are already on a V2 generation, which implies an earlier shipped generation and continued iteration.
Launched: Renidly rebrand in 2026 (footer '© 2026 Renidly'; rebrand banner live over an Apr 4 2026 post). The predecessor LinkdAPI job and professional-identity API predates that but no founding or first-launch date appears anywhere gathered — treat the original launch as ~2023-2025, with 'V2' endpoint naming as the only internal evidence of a prior generation.
Delivery: not stated
Entity mapping: not stated
Sample: not stated
Point-in-time: not stated
Licence: not stated

supplier index read from their site