LinkedIn Data API — Try the interactive demo

Search by the required name keyword, then narrow matches with current_company, past_company, title, geocode_location, school, industry or profile_language. Company, location and several other filters accept comma-separated IDs. A successful live response returned data records with id, urn, public_identifier, full_name, title, location, url, avatar and profile flags, plus page, total and has_more. Use the returned public_identifier for a profile lookup; a name match alone does not establish identity.

Pass the public username from a LinkedIn /in/ profile URL, not the entire URL or display name. A successful live lookup returned data.id, urn, public_identifier, full_name, headline, location, avatar, cover, profile flags, website and locale fields. Optional include_* booleans request additional sections and can increase request consumption. An inaccessible or nonexistent profile was observed with HTTP 200, success:false, data:null and status_code:403; early HTTP 202 responses also carried business failures. Check success and message before using data.

Supply a company name or public company slug in company, or a numeric company_id. Provide at least one identifier; both parameters are individually optional because they are alternatives. The successful Google lookup returned data.id, name, universal_name, description, linkedin_url, website_url, active, employee_count, employee_count_range, follower_count, headquarter, locations, industries, specialities, logo and cover. Counts describe reported profile data, not verified payroll headcount. Using company_id can increase request consumption; inspect business success when a lookup is throttled or inaccessible.

Search with a required keyword and optional geocode, company ID, date_posted, remote, experience_level, job_type and other listing filters. The live first-page response contained 25 data records with id, title, url, listed_at, location, is_easy_apply, is_promote and a company object with id, name, url, verified and logo. The response also supplied page, total, has_more and metadata echoing the keyword and location filter. Iterate page numbers, deduplicate by job id and stop according to returned continuation signals; the reported total does not guarantee every listing is retrievable.

Pass a public username to read available professional contact information. The documented data object contains first_name, last_name, public_identifier, urn, email, phone_numbers, websites, twitter, address and wechat; some values are null or empty arrays. Availability varies, and a returned email is not evidence that it is verified or that its owner consented to outreach. Use only permitted fields in consent-managed workflows and provide appropriate retention and deletion controls.

Supply username to retrieve count-only audience context. The documented result has data.follower_count and data.connection_count in the usual success/message response. It does not contain lists of followers or connections, relationship details, or historical growth. Save dated observations in your application when a participating creator needs a trend report.

Pass the urn returned by a profile lookup to retrieve account-context metadata. The documented data object contains joined, profile_photo and contact_information as human-readable date or recency strings. This is the About this profile surface, not biography text or proof of identity. Values may use relative wording and should be retained as returned rather than converted into unsupported precise timestamps.

Supply username to retrieve a profile PDF for an authorized review workflow. The documented successful response is a PDF document beginning with %PDF, not the usual JSON success/data object. Handle the returned document payload as a file rather than assuming profile fields can be parsed from JSON. The documentation sample establishes a document response, not universal download availability or a guarantee that every current profile section appears in the export.

Use company_id and page to request available people summaries associated with a company. The documented data array contains full_name, title, location, services, is_premium and optional avatar metadata; some entries explicitly use LinkedIn Member with id, url and urn set to null. page, total and has_more accompany the list. Preserve anonymized records and null identifiers; this is not a guaranteed complete or verified employee roster.

Pass company_id to retrieve available affiliated or showcase pages. The documented data array includes id, name, type, universal_name, linkedin_url, speciality, follower_count and logo variants with size and expiration metadata. Preserve page type when relating these records to a parent company; a showcase page is not necessarily a separate legal entity.

Supply company_id to retrieve aggregate associated-member categories. The documented data array has title and insights; each insight contains name and count. Examples include Locations, School, Current Function, Skill Explicit and Service categories. These are profile-association distributions, not verified personnel statistics. Categories can overlap, especially geographic regions, so their counts should not be summed into a headcount.

Supply job_id from a job-search or company-jobs result. The documented sample has a data object with id, title, description, company, country_code, location, location_geocode, employment_status, level, listed_at, expire_at, job_url, workplace_types, work_remote_allowed and salary metadata. include_skills requests additional skill information and can increase request consumption. The salary object includes salary_exists and may not describe a usable pay range. This endpoint retrieves a listing; it does not submit an application.

Pass company_id and an optional page. Narrow the employer feed with date_posted, remote, experience_level, job_type and boolean listing filters. The documented response contains data rows with job id, title, url, listed_at, location, is_easy_apply, is_promote and company details, plus page, total, has_more and metadata.companyId. This is an employer-scoped listing read; it does not apply to jobs or guarantee the completeness of a company's openings.

Supply a company_id to retrieve the reported number of jobs for that company. The documented JSON body contains success, message, process_time, cost and data.total. This count-only operation does not return job rows or a built-in history. Record your own collection timestamp when comparing results over time, and do not equate a change in listed jobs with a change in actual hires.

Use a profile urn and optional page to retrieve available work-experience entries. The documented data array contains title, employment_type, date.start, date.end and company objects with id, name, url and logo. The response includes page, total and has_more. Preserve returned date wording and missing values; a listed role is self-reported professional context, not an independently verified employment record.

Supply a profile urn and page to request available education entries. The documented data array has school, degree and date.start/date.end, with page, total and has_more outside the array. Use these fields as editable, self-reported education context; the response does not verify attendance, graduation or accreditation.

Pass a profile urn with optional page to read available listed skills. The documented data entries contain skill and num_endorsements, accompanied by page, total and has_more. These are profile-listed skills and counts, not a standardized proficiency assessment. Use them in editable, human-reviewed inventories rather than as automatic hiring qualifications.

Use urn from a selected profile and optional page to retrieve available credential listings. The documented data entries contain title, authority, issued_at and credential_url, with page, total and has_more. A credential listed on a profile is not independently verified or necessarily current; use a returned credential_url for appropriate issuer-side or human verification.

Supply a profile urn and optional page for available honors and awards. The documented data array includes title, issued_by, issued_at and associated_with, plus page, total and has_more. These entries describe profile-listed recognition; they do not independently prove an award was granted or establish a ranking.

Pass a profile urn and optional page to read available publication entries. The documented data array includes title, publication, publication_url, description and date. page, total and has_more describe continuation. This is a profile publication section, not a complete scholarly citation index or a guarantee of peer review.

Use a profile urn and optional page to request available volunteer entries. The documented data array includes title, organization, cause, description, duration and date.start/date.end, together with page, total and has_more. Volunteer causes can be sensitive. Restrict use to user-approved portfolio or community-contribution workflows and avoid sensitive-interest profiling or automated employment decisions.

Supply urn, optional page and type=received or given. A pagination_cursor can be forwarded when continuation data is available. The documented data array contains date, text, type and recommender profile context, including names, description, public_identifier, url and avatar. The sample also includes page, total and has_more. Recommendations are profile text, not independently verified references; preserve the returned type instead of assuming every record is received.

Pass a profile urn with optional page to retrieve available company-interest entries. The documented data array contains id, title, url, follower_count and logo metadata. Pagination uses page, total and the camel-case hasMore field. A company interest is not proof of employment, buying intent or consent to contact; use it only in appropriately governed professional-interest workflows.

Supply urn and optional page to request available group-interest entries. The documented data array includes id, title, url, member_count and logo, plus page, total and hasMore. A returned group ID can be used for group-info research, but an interest entry does not grant membership or access to private group discussions.

Use a required keyword with optional page, sort_by, date_posted, content_type, from_company and from_member. The documented data records include id, title, url, created_at, author and activity counts, plus page, total and has_more. Post date values use past_24h, unlike the past_24_hours value for job searches. Retrieve a selected post separately when fuller text or attachment details are needed.

Pass post_id to retrieve a selected post. The documented data object contains id, text, created_at, url, author, content and activity. content holds attachment-specific fields that can be null; activity includes num_comments, num_likes, num_shares and reaction_counts. These are observed engagement values at retrieval time, not impressions, reach, sentiment analysis or a built-in historical series.

Supply company_id, optional page and sort_by=top or recent. The documented data array contains post id, text, created_at, url, share_urn, author, content and activity, with page, total and has_more. The author object describes the company page; available attachments and reaction counts vary by post. The documented default sort is top, so select recent explicitly for a chronological monitoring workflow.

Use the profile urn with optional page and pagination_cursor. The documented data array contains id, text, created_at, url, share_urn, author, content and activity; the response also has page and pagination_token. Supply a returned pagination_token through the public pagination_cursor field for continuation. This sample does not expose the same has_more/total contract as company posts, so do not assume uniform pagination across feeds.

Supply a profile urn, optional page and pagination_cursor to read available comment activity. The documented entries contain comment, created_at, is_edited, urn, activity and an associated post object with its own id, text, author, content and url. The response includes page and pagination_token. Keep a user's comment activity distinct from the full comment thread of the associated post.

Pass a profile urn and optional page or pagination_cursor to request available reacted-post records. The documented data entries contain reaction_type and a nested post with id, text, url, author, content, created_at and activity. The response includes page and pagination_token. A reaction is an interaction record, not consent to outreach or reliable evidence of a sensitive interest.

Supply a profile urn with optional page and pagination_cursor. The documented data array contains id, created_at, url and images with media variants, dimensions and expiration metadata. The response includes page and pagination_token. These are available image-post records, not the profile avatar endpoint or a guarantee that media URLs remain usable indefinitely.

Use urn and optional page or pagination_cursor to request available video-post records. The documented data entries include id, created_at, duration, thumbnail, url and activity counts; duration is represented as a string in the sample. page and pagination_token support continuation. The observed documentation does not establish video downloads, watch time or impression analytics.

Supply post_id with optional post_type, page and sort_order. The documented data entries include id, urn, comment, commenter, created_at, num_replies, replies, previous_replies_token, reaction_counts and edit, pin or author flags. page, total and has_more describe the comment page. Retain parent comment IDs and returned reply continuation data when a separate request is needed for additional replies.

Provide post_id, comment_id and replies_cursor copied from the parent comment's previous_replies_token. All three inputs are required; the cursor is thread-continuation data, not an account login token. The documented data array contains comment, commenter, created_at, urn, num_replies, reaction_counts and edit, pin or author flags, with page, total and has_more. Attach replies to the originating comment rather than merging unrelated discussion threads.

Pass post_id, optional page and type to retrieve available reaction records. Supported type values are all, like, praise, empathy, appreciation and interest. The documented data entries have reaction_type and user context including id, name, description, url, urn and avatar; page, total and has_more accompany the result. A reaction record does not grant permission to contact the person or establish buying intent.

Use post_id with optional page and pagination_cursor. The documented data entries contain id, author, activity, is_repost_quote, text and created_at; text and created_at can be null. page, total, has_more and pagination_token accompany the list. Forward returned pagination_token as pagination_cursor when continuing. These are available repost records, not a complete propagation graph or proof that each share includes commentary.

Supply keyword or advertiser_name; at least one is needed even though each field is individually optional. Add country, date and pagination_cursor to narrow or continue the search. The documented data array contains id, ad_url, advertiser, content_preview and image, with has_more and pagination_token. Forward a returned pagination_token through pagination_cursor. These records support creative research, not spend, targeting, reach or conversion measurement.

Pass ad_id obtained from ad-library search. The documented data object includes id, ad_type, ad_url, content, image, advertiser, publisher and paid_for_by. advertiser and publisher contain name and url in the sample. Keep the advertiser, publisher and payer roles distinct; the result is an available creative record, not an ad-account report or evidence of spend and conversions.

Pass group_id to retrieve available group metadata. The documented data object includes id, urn, name, description, industries, member_count, is_public, is_active, created_at, activity, rules, post_approval_enabled, owners, logo and cover. Metadata access is not membership and does not imply access to private posts. Use group identifiers already known to or appropriately selected by your application.

Supply group_id with optional page to request available group discussions. The documented data array contains post id, text, created_at, url, share_urn, author, content and activity; page, total and has_more describe continuation. Some attachment fields can be null. Availability is limited to what the response actually supplies and does not establish access to private groups or every historical discussion.

Supply a human-readable keyword such as a city or country name. The documented JSON response has success, message, process_time and data entries containing location and geocode. Choose the intended location from possible matches before using its code. Job search accepts geocode, while people search names its location filter geocode_location; do not substitute display labels for codes.

Use keyword and optional page to discover institution records. The documented data array contains id, name, universal_name, location, students, url and logo, with page, total and has_more. Select a matching institution before using its ID as a people-search school filter. students is a display string in the sample rather than a verified enrollment number.

Pass an industry keyword to retrieve available industry suggestions. The documented response contains data records with name and industry_id, plus success, message, process_time and cost. Use the selected IDs as industry in people search or industry_ids in job search. This lookup does not itself return companies, people or jobs and does not define a paginated listing contract.