LinkedIn reference
LinkedIn API guide
Research a public company or professional profile, then retrieve the relevant posts or profile sections. Company and member identifiers are not interchangeable.
Quickstart
Start with LinkedIn
Research a public company or professional profile, then retrieve the relevant posts or profile sections. Company and member identifiers are not interchangeable.
These requests use your API key and can spend credits. Check the current price on the endpoint page; each new page is a separate request. Later examples use illustrative identifiers: replace them with values from your earlier response.
1. Resolve a company
Read the returned company identity before using its name as an entity match. Parameters and current cost →
curl "https://www.monocrawl.com/v1/linkedin/company?url=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fnasa%2F" \ -H "x-api-key: mn_your_key_here"
2. Collect company posts
Keep the returned continuation unchanged. Select a post URL for the detail lookup. Parameters and current cost →
curl "https://www.monocrawl.com/v1/linkedin/company-posts?url=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fnasa%2F" \ -H "x-api-key: mn_your_key_here"
3. Read a post with comments
Use a selected post URL. One comments page can be included at the normal post price; inspect comments_status and partial. A comments preview is not the entire discussion. Parameters and current cost →
curl "https://www.monocrawl.com/v1/linkedin/post?url=https%3A%2F%2Fwww.linkedin.com%2Ffeed%2Fupdate%2Furn%3Ali%3Aactivity%3A7500971887234097153&include_comments=true" \ -H "x-api-key: mn_your_key_here"
Filters and coverage
Choose filters with the source behavior in mind
| Control | Behavior and limits |
|---|---|
| Entity type | Company URLs and member URLs target different operations. Keep source identifiers alongside names when joining results. Endpoint reference → |
| Company by website | Supply domain instead of url to check up to three indexed company pages against their returned website host. domain_lookup.exact_matches counts distinct native company IDs; exact_match_pages counts verified pages. verified_candidates includes checked IDs, names, URLs, websites and matched_urls. Aliases merge only when the source IDs agree. Distinct companies sharing a domain remain ambiguous; inspect error.details.domain_lookup and choose an explicit company URL yourself. This is bounded indexed discovery, not native LinkedIn company search or proof of domain ownership. Endpoint reference → |
| Company continuation | Use the returned cursor instead of incrementing or decoding it. Keep the company URL with it; do not supply a competing page value. The declared page range is bounded and does not imply all company history. Endpoint reference → |
| Larger result windows | Profile posts, company posts, post comments and post reactions accept pages=1, 2 or 3 at their normal public price. The total deadline and spending limit still apply; inspect pages_fetched, partial and window_stop_reason. Keep pages, target and filters unchanged with the returned cursor. A short or filtered page can still have continuation. Endpoint reference → |
| Profile section lookup | Use a public profile URL or a confirmed member URN. URL requests resolve a matching public identity within the existing request limits. Only the identity is reused; a fresh section request still fetches its section. Empty sections are free and do not establish that a complete profile is available. Image and video cursors carry their continuation token; send the cursor back unchanged. Endpoint reference → |
| People search by URL | Supply search_url for a public LinkedIn people-search URL with keywords and supported single-value filters. Unsupported, multiple-choice, network or Sales Navigator filters are rejected before collection. This translates the search; it does not use a logged-in account or its private network. Endpoint reference → |
| Profile coverage | A profile and its experience or education sections are distinct from recent posts and engagement lists. Returned section counts do not guarantee full historical coverage. Endpoint reference → |
| Discussion | Comments, reactions and reposts are different endpoints and populations. A comments_preview field on a post is only a preview. Endpoint reference → |
| Optional discussion bundle | include_comments=true keeps the normal post price and shared spending/time limit. If comments fail, comments_page is null and partial=true while the usable post keeps its normal charge. It does not promise every comment. Endpoint reference → |
| Matching and completeness | hashtag matches exact tags in text on one keyword-search page. Returned counts are not platform-wide totals, and no additional pages are fetched just to fill a filtered page. Endpoint reference → |
| Already supplied detail | employees_count is a returned company headcount, not a location breakdown. similar_pages, funding and other optional fields are preserved when supplied; null means unavailable, not zero. Endpoint reference → |
Source availability, ordering and field coverage can change. Inspect warnings and partial-result metadata alongside the rows. See runnable workflows, metric semantics, computed fields and the pagination matrix.
Choose an endpoint
Match the operation to your task
| Your task | Endpoint | When to use it |
|---|---|---|
| A member profile | profile | Use a public member URL. top_position follows source display order; it is not verified current employment. position_skills contains only skills tied to supplied jobs. |
| Exact hashtag matches | search-posts | Pass hashtag instead of query. Only matching posts in the returned search page are kept; follow continuation after an empty filtered page. |
| More member posts | profile-posts | pages=3 requests up to three pages within the normal price and limits. Inspect the stop reason and continuation; this is not a full archive. |
| Profile with posts | profile/full | Use an /in/ URL for a person or /company/ URL for a company. Includes one posts page and explicit partial-result billing. |
| Discussion under a post | post-comments | Continue a comments_page.next_request here at this operation’s normal price. |
| Member experience history | profile-experiences | Read a specific profile section and its own continuation. |
Explore all documented operations by purpose below. Each endpoint reference contains its accepted parameters and current price.
Comments and replies
Other operations
Posts and media
Accounts and audiences
company-profileprofileprofile-certificationsprofile-contactprofile-educationsprofile-experiencesprofile-freshnessprofile-honorsprofile-imagesprofile-interests-companiesprofile-interests-groupsprofile-postsprofile-publicationsprofile-reactionsprofile-recommendationsprofile-skillsprofile-statsprofile-videosprofile-volunteersprofile/full
Transcripts
Operations
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Elsewhere
The same registry, other shapes
- LinkedIn overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=linkedin— the same rows to your code at runtime, for 0 credits.