Linkedin Video Downloader

Linkedin Video Downloader prepares one accessible LinkedIn post containing video as normalized metadata and can optionally store the available media file in Apify.

• Two public inputs cover one LinkedIn post URL and an optional download preference.
• Four quality values provide metadata-only, low, medium, and high processing modes.
• Successful records follow a 39-field Dataset contract with thumbnail-first display.
• Comment retrieval is not exposed; the reserved comments array is normally empty.

Run one LinkedIn post test

View the Apify API

Publish the Actor, replace the illustrative post URL, and test metadata before file delivery.

Why Choose This API

Linkedin Video Downloader defines a small processing contract for one public LinkedIn post with video. Available source values are mapped to stable fields for video identity, author, publication time, thumbnail, duration, engagement counters, dimensions, audio labels, and run provenance.

Metadata mode avoids transferring media. A low, medium, or high selection requests an available rendition and can store the file. Source encodes determine the actual result; a preference is not a guaranteed resolution.

The contract is different from LinkedIn profile, company, jobs, events, course, feed, search, or comment extraction. Although the local yt-dlp list contains LinkedIn, events, and learning extractors, this Actor documents only one post URL. That narrow claim still requires representative live validation.

Quick Start Guide

The same illustrative post is used throughout:

{
  "video_url": "https://www.linkedin.com/posts/leidos_ifpc-increment-2-launch-video-activity-7358191055076294656-42wv",
  "video_quality": "metadata"
}

Replace the placeholder with a current public post you are authorized to process. Open it in a private browser window; a post visible only when signed in does not satisfy the public contract. Submit metadata mode and verify ID, author, thumbnail, and title or description.

Only request a file after the returned identity matches. A rendered HTML page or succeeded run is not enough if the expected video record is absent. Use separate runs for multiple posts.

Input Parameters

Parameter	Type	Required	Purpose
video_url	string	Yes	One accessible LinkedIn post URL containing video.
video_quality	string	No	metadata, low, medium, or high; metadata skips storage.

The URL field has the matching placeholder prefill and example. The optional quality field has no prefill or example; when omitted, the runtime uses metadata mode.

No profile, company, course, event, job, feed, query, date, login, cookie, country, batch, or comment option exists. Additional input properties are rejected.

Output Data Schema

The Dataset exposes 39 possible fields:

Area	Fields
Video identity	thumbnail, id, platform, title, description, duration, published_at
Publisher	author, author_id, author_url
Labels and counters	categories, tags, view_count, like_count, shares_count, dislike_count, comment_count
Technical media	width, height, fps, audio_title, audio_artist, video
Reserved and provenance	comments, processed_at, processor

An abbreviated shape for the same placeholder is:

{
  "id": "0000000000000000000",
  "platform": "LinkedIn",
  "title": "Example LinkedIn video post",
  "author": "Example publisher",
  "thumbnail": "https://example.com/linkedin-thumbnail.jpg",
  "comments": [],
  "video": ""
}

This is a schema illustration, not observed output. LinkedIn may expose only a subset of fields to guests, so nulls are expected. Metadata mode returns no stored file. The public input does not retrieve post comments.

Source-dependent fields also present in every item:

Field	Meaning
source_url	Canonical page URL of the item on its own platform
media_type	Kind of media the source reports, such as video or audio
live_status	Whether the item is a recording, currently live, or a finished stream
availability	Source visibility, such as public, unlisted, or needs_auth
age_limit	Minimum viewer age the source enforces; zero means no restriction
language	Primary language of the item as reported by the source
followers	Follower or subscriber count of the author at processing time
is_verified	Whether the author's account carries a verified badge
saves_count	Times viewers saved the item, on sources that expose it
file_ext	Container extension of the selected media, such as mp4 or webm
file_size	Size of the selected media in bytes, exact or approximate
subtitles	Language codes of published subtitle tracks; auto-captions excluded
chapters	Chapter markers with title and start and end time in seconds

Integration Examples

The intended reference is agentx/linkedin-video-downloader.use the same scenario over HTTP:

curl -X POST "https://api.apify.com/v2/acts/agentx~linkedin-video-downloader/runs?token=$APIFY_TOKEN" \
 -H "Content-Type: application/json" \
 -d '{"video_url":"https://www.linkedin.com/posts/leidos_ifpc-increment-2-launch-video-activity-7358191055076294656-42wv","video_quality":"metadata"}'

The matching hosted MCP configuration is:

{
  "mcpServers": {
    "apify-linkedin-video": {
      "url": "https://mcp.apify.com?tools=agentx/linkedin-video-downloader",
      "headers": {
        "Authorization": "Bearer <APIFY_TOKEN>"
      }
    }
  },
  "exampleToolArguments": {
    "video_url": "https://www.linkedin.com/posts/leidos_ifpc-increment-2-launch-video-activity-7358191055076294656-42wv",
    "video_quality": "metadata"
  }
}

Publication is required for discovery. Protect the token and follow the Apify MCP documentation.

Pricing & Cost Calculator

Local metadata declares these events, not a verified Store offer:

Event	Billing unit	Local price
actor_usage	Metered runtime, proxy, and storage usage	$0.00001
metadata	One successfully processed metadata result	$0.13
download	One successfully processed result with stored video	$0.30

The smallest metadata result declares $0.13 plus metered usage. A download result declares $0.30 plus metered usage.

Use Cases & Applications

Communications teams can preserve an authorized company announcement video with source identity and processing time. Researchers can document one public professional-media post. Developers can send the Dataset item to a webhook or catalog. AI teams can pass a permitted stored file to a separate transcription service.

Repeated metadata runs can observe currently exposed counters, but the Actor does not calculate changes or deduplicate. Keep the source URL and media ID with every result. A previously accessible post can later require login or be removed.

Limits & Troubleshooting

LinkedIn frequently varies guest access. Sign-in walls, deleted posts, member privacy, company controls, geography, rate limits, or platform changes can prevent extraction. The Actor exposes no LinkedIn credential or cookie input.

If no item appears, replace open the exact post in a private window, confirm that it contains video, and retry metadata mode. Do not submit a profile, company, course, event, or feed URL.

If a download run has no video, inspect logs and storage, then retest metadata. Before release, run public video, text-only, login-gated, removed, malformed, and download cases. Check all 26 output keys and the intended media identity.

FAQ

Can it scrape a LinkedIn profile or company?

No. Use a dedicated AgentX lookup Actor for those entities.

Does it process LinkedIn Learning courses or events?

No. Those local extractors are not part of this public post contract.

Can it retrieve post comments?

No comment input exists; the reserved list is normally empty.

Can it bypass a sign-in wall?

No login or cookie field is exposed.

Does high guarantee a resolution?

No. The post’s available renditions determine the result.

Why are fields null?

The guest-visible source did not expose them. Null is not zero.

Can it run on a schedule?

Yes, but access and post availability can change.

Which LinkedIn post URLs can be processed?

Use a public linkedin.com/posts/<slug>-<activity-id>-<code> permalink whose primary attachment is a native video. Posts behind a sign-in wall, LinkedIn Learning lessons, and event pages sit outside this contract, and no credential input exists to reach them.

Legal & Responsible Use

Process only posts you are authorized to access, download, and retain. Public visibility does not grant reuse rights. The caller is responsible for LinkedIn terms, copyright, privacy, law, and retention policy.

Related Tools

• LinkedIn Company Lookup handles company information.
• LinkedIn Profile Lookup handles person profile information.
• LinkedIn Jobs Scraper handles job listings.
• All Video Scraper accepts supported URLs from multiple video hosts.

Support & Community

• AgentX community
• Contact the AgentX team
• Apify Actor dashboard
• Apify API reference
• Apify MCP documentation

Include the stable ID, redacted post URL, access condition, input, and run ID in support requests.

Run one LinkedIn post test

View the Apify API