What this API does and who it is for
The Bulk data enrichment API targets developers who need to extract structured data from LinkedIn — profiles, companies, posts, and engagement threads — without managing their own scraping infrastructure. The pitch is straightforward: submit a request, receive LinkedIn data in near-real-time. With over 10,000 marketplace subscribers and a popularity score of 9.9 out of 10, it is clearly widely adopted.
That said, the API is not a clean, purpose-built LinkedIn connector. Its 87 endpoints also include a variety of utility and novelty endpoints — jokes, cat facts, dog images, trivia questions, number facts, and JSON placeholder responses — alongside the LinkedIn-focused core. The practical consequence for a developer is that the surface area of the API is broader and more heterogeneous than the name implies, so careful endpoint selection matters.
Endpoint walkthrough
The LinkedIn-relevant endpoints are the reason most developers will be here. The key ones are:
/profiles— Fetch one or more LinkedIn member profiles/person— Retrieve individual person data/companies//company— Pull company-level records/profile_posts— Retrieve posts published by a given profile/company_posts— Pull posts published by a company page/comment_replies— Fetch replies within comment threads/profile_updates— Access recent activity or updates from a profile/search_geourns//suggestion_geourns— Work with LinkedIn geographic URN identifiers, useful when building location-filtered queries/suggestion_function//suggestion_language— Retrieve autocomplete-style suggestions for job functions and languages, which can help when constructing search filters
Many of the core endpoints are exposed as both GET and POST, giving some flexibility in how you pass parameters. The non-LinkedIn endpoints (/joke, /dog_fact, /shuffle, etc.) appear bundled in the same namespace; they may be useful for testing connectivity or basic integration checks, but they are not core to the data enrichment use case.
The /docs endpoint ostensibly serves documentation, though the provider's listed support channel is simply a direct message — there is no detailed public API reference to reference here beyond the endpoint list itself.
Pricing breakdown
| Plan | Price | Monthly requests | Rate limit | Overage |
|---|---|---|---|---|
| BASIC | $0 / month | 150 | — | None |
| PRO | $40 / month | 20,000 | 1 req / sec | None |
| ULTRA (recommended) | $100 / month | 60,000 | 10 req / sec | $0.0020 / req |
| MEGA | $400 / month | 400,000 | 25 req / sec | $0.0010 / req |
The BASIC tier's 150 requests per month is a proof-of-concept allowance at best. If each request fetches one profile, you can evaluate the response shape and data quality, but you cannot run any sustained enrichment workflow at this volume.
PRO at $40/month with 20,000 requests fits light use cases — small CRM enrichment runs, occasional company lookups, or background jobs that don't need high throughput. The 1 request-per-second cap will be a constraint if you are processing batches quickly.
ULTRA jumps the rate limit to 10 req/sec and 60,000 monthly requests with an overage option at $0.002 per additional call. This is the provider's recommended tier and makes sense for teams running regular enrichment pipelines. The overage pricing means you won't hit a hard cutoff mid-run, which matters for batch jobs.
MEGA at $400/month with 400,000 requests and a 25 req/sec ceiling is for high-frequency or bulk enrichment at scale. The overage rate drops to $0.001 per request here, halving the marginal cost compared to ULTRA.
Practical use cases
- Sales intelligence enrichment: Pipe a list of LinkedIn profile URLs through
/profilesor/personto augment CRM records with current job titles, company, and location. - Company research: Use
/companiesand/company_poststo monitor what organizations are publishing, useful for competitive intelligence workflows. - Recruitment tooling: Combine profile lookups with geographic URN filtering via
/search_geournsto build candidate shortlists. - Social listening on LinkedIn:
/profile_updatesand/comment_repliesenable tracking of what specific accounts are posting and how their content is being discussed.
Limitations and things to check before integrating
The single most important number in the API's fact sheet is the 69% average success rate. For a data enrichment workflow, roughly one in three requests failing means you need robust retry logic and error handling before you can rely on this in production. At the MEGA tier's 25 req/sec, that error rate compounds quickly in batch jobs. Before committing to a paid plan, test your specific target data (profile types, company sizes, geographic regions) under the BASIC tier and measure the success rate for your actual use cases — aggregate platform numbers may mask variance.
Average latency of 1,297 milliseconds (about 1.3 seconds per call) means synchronous, user-facing enrichment is unlikely to be viable. Architect any integration as an asynchronous background process with a queue, not as a real-time API call in a request lifecycle.
The endpoint list duplicates several routes (both GET and POST variants of /joke, /cat_fact, /shuffle, and others), which suggests the API surface was assembled broadly. Confirm the exact parameter schemas through the /docs endpoint or by testing, since the provider's documentation is minimal.
Finally, scraping LinkedIn programmatically carries platform terms-of-service considerations that sit outside this API's control. Developers should review their own compliance obligations before building production systems on top of scraped LinkedIn data.
Getting started
Subscribe to the BASIC plan to get your API key at no cost. Use that 150-request budget to hit the core endpoints you actually need — /profiles, /companies, or /company_posts — and validate the data structure and completeness for your target records. Pay particular attention to which fields are populated and how often you receive error or empty responses; this will give you a realistic picture of what the 69% success rate means for your specific workload before you upgrade to a paid plan.
