Download LinkedIn Video API

One authenticated POST request downloads a video from a public LinkedIn post and returns a persistent MP4 link — ready for media pipelines and content workflows.

One REST Endpoint
Quality Control
Persistent Download Link
Structured JSON Output
Predictable Error Codes
Samples In Five Languages

Tool API Agent

Request examples

View API docs Full API reference

curl -X POST "https://api.agentbody.io/v1/linkedin/video/download" \
  -H "Authorization: Bearer <YOUR_AGENTBODY_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{"quality":"360","url":"YOUR_URL"}'

Response examples

Documented responses from the OpenAPI specification.

Retained LinkedIn video link and normalized metadata.

{
  "format": "mp4",
  "post_id": "7344462117049131012",
  "post_url": "https://www.linkedin.com/posts/ryanrolds_signull-x-google-maps-activity-7344462117049131012-AZXC/",
  "quality": "480",
  "video_content_type": "video/mp4",
  "video_url": "https://api.apify.com/v2/key-value-stores/example/records/7344462117049131012.mp4"
}

Features

Use the Download LinkedIn Video API to save videos from public LinkedIn posts as MP4 files with persistent download links for media pipelines, content archives, and research workflows.

One REST Endpoint

Call POST /v1/linkedin/video/download with a bearer API key and a public post URL. The LinkedIn video download API processes the post and returns a persistent MP4 link through a documented HTTP request, so your application can save videos without maintaining a browser-driven scraper or an unofficial client SDK.

Quality Control

Specify 360p, 480p, or 720p in the request body to control file size and clarity. Lower quality reduces bandwidth and storage costs; higher quality preserves detail for presentations or archives. The default is 480p.

Persistent Download Link

Every successful response returns a stable video_url that you can open, save, or pass to downstream services. The link persists after the request completes, so you can retrieve the file later or share it across your pipeline.

Structured JSON Output

Receive post_id, post_url, video_url, video_content_type, format, and quality in a predictable JSON response. This structure fits services that store media records, build archives, or feed downstream processing pipelines.

Predictable Error Codes

Handle failures with documented status codes: 400 for an invalid request, 401 for a missing or bad API key, 402 for insufficient balance, and 502, 503, or 504 for temporary upstream issues. Each response identifies the problem class, so retry and alerting logic stays simple.

Samples In Five Languages

This page generates request examples in curl, JavaScript, Python, Java, and Go directly from the API's OpenAPI definition. Adopt the language and HTTP client your stack already uses, and keep the integration as one standard authenticated POST.

How to use

Follow these six steps to call the Download LinkedIn Video API, pass a public post URL with quality, and process the returned MP4 link in your application.

Create An API Key

Create an AgentBody account and generate an API key in the console. Keep the key in your server environment or an approved secret store and send it as a bearer token. Never place a live key in browser code, public repositories, or client-side bundles.

Choose A Public Post

Pick the public LinkedIn post containing the video you need and copy its URL. Private posts, deleted content, and posts without videos will not resolve — prepare alternates when your workflow needs coverage.

Build The POST Request

Send an authenticated POST request to /v1/linkedin/video/download with the url and optional quality in the JSON body. The generated examples on this page show the exact request in curl, JavaScript, Python, Java, and Go for the HTTP client your service already uses.

Keep The Key Server-Side

Call the endpoint from your backend, a serverless function, or a scheduled job — anywhere the API key stays out of the browser. If you expose the download to end users, proxy it through your own endpoint so the key and billing stay under your control.

Parse The JSON Response

Read the returned post_id, post_url, video_url, video_content_type, format, and quality fields. Store only the fields your product needs, keep the post URL paired with its download link, and align retention with your own privacy policy.

Handle Errors Correctly

Fix 400 responses by correcting the request, 401 by configuring a valid key, and 402 by topping up balance. Retry 502, 503, and 504 responses with backoff, since they indicate temporary upstream conditions rather than a permanent problem with the post.

Frequently asked questions

What is the Download LinkedIn Video API?

The Download LinkedIn Video API is an authenticated POST endpoint, /v1/linkedin/video/download, that saves a video from a public LinkedIn post and returns a persistent MP4 download link. Send a public post URL with your bearer API key and process the response in your application.

Is there a free LinkedIn video download API?

You can start with a free AgentBody account, and every call runs on your account's credits, so the API is free to try before committing to volume. Usage-based pricing is governed by the gateway rather than fixed numbers on this page — check the console for current per-call costs.

Can this replace a LinkedIn video downloader scraper setup?

Yes. Instead of maintaining a LinkedIn video downloader scraper with browser automation, proxies, and parsing code, you call one documented REST endpoint and receive a stable MP4 link. The API reads public posts only, so it is not a way around private or deleted content.

What does the LinkedIn video API response include?

A successful response includes post_id, post_url, video_url, video_content_type, format, and quality. The video_url field carries the persistent MP4 download link. Use these fields directly in storage, media pipelines, or archive workflows.

Does the API support HD quality downloads?

Yes — pass quality as 720p in the request body for the highest available resolution. Lower options (360p, 480p) produce smaller files for bandwidth-constrained pipelines. The default is 480p.

How do I handle API errors?

Correct the request shape on 400, fix your bearer key on 401, and resolve balance on 402. Treat 502, 503, and 504 as temporary upstream failures and retry with backoff. Log the status and error code before retrying so your pipeline can distinguish bad requests from transient issues.