LinkedInVideo TranscriptsCaptionsSocial ListeningAPI Guide

LinkedIn Video Transcript API: Turn LinkedIn Video Captions Into Text

Get the words spoken in LinkedIn videos as plain text from the post URL. Send post URLs in bulk and pay 0.7 credits per captioned video returned.

SocQUpdated November 19, 20265 min read

Founders and executives increasingly speak on LinkedIn video instead of writing long posts. Product demos, talks and earnings recaps end up as videos, and a pipeline that only reads post text misses what was said in them.

On 2026-11-17 SocQ added the LinkedIn Video Transcript API. Pass the post link and the transcript comes back from the captions attached to the video, as plain text ready to quote, summarize or search. This guide covers the request, the response, the price and how to fit it into an existing LinkedIn workflow.

Quick answer: Send LinkedIn post URLs that contain a video in urls to POST /v1/linkedin/post-transcript. Poll GET /v1/tasks/{task_id} and read one row per captioned video from data.results.items, with the caption text in text. Each transcript returned costs 0.7 credits ($0.0035).

What the Endpoint Returns

1 SocQ credit = $0.005.

EndpointWhat it returnsPrice
LinkedIn Video Transcript APIOne row per captioned LinkedIn video: the caption text as plain text, the post URL, and the transcript language, format and duration when available0.7 credits ($0.0035) per transcript returned

Billing follows the transcripts returned, so you pay for captioned videos that produce a row.

Authentication and the Async Task Flow

All SocQ requests authenticate with an API key, and the same header is used for submit, task status and result requests:

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Every collection runs as a background task:

submit -> task_id -> queued -> running -> succeeded
                                   \-> failed

The submit response contains data.task_id and data.status. Poll the task with that ID:

curl "https://api.socq.ai/v1/tasks/$TASK_ID?limit=50" \
  -H "Authorization: Bearer $SOCQ_API_KEY"

When status is succeeded, the response includes the first page of normalized records in data.results.items. limit defaults to 50 and goes up to 500; if has_more is true, pass results.next_cursor as cursor to read the next page. While a task is queued, running or failed, the endpoint returns task metadata without results.

An optional callback_url in the submit body makes SocQ send one POST with a task summary when the task finishes; read the records with GET /v1/tasks/{task_id}. A client-side timeout does not cancel a task, so resume with the same task ID instead of paying for a duplicate. 402 means insufficient credits; 429 means the key hit a rate or credit limit.

Request a LinkedIn Video Transcript

Provide LinkedIn post URLs that contain a video in urls. Both URL forms work: /posts/... and /feed/update/urn:li:activity:....

curl -X POST "https://api.socq.ai/v1/linkedin/post-transcript" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "urls": [
      "https://www.linkedin.com/posts/satyanadella_keeping-over-a-million-elevators-and-escalators-activity-7518982780551340032-z4go"
    ]
  }'

SocQ may reserve credits based on the number of submitted URLs and settles the final charge from the actual result_count once the task finishes, returning any unused credits.

Understand the Transcript Record

The documentation example returns this row (text shortened):

{
  "id": "https://www.linkedin.com/posts/satyanadella_keeping-over-a-million-elevators-and-escalators-activity-7518982780551340032-z4go",
  "platform": "linkedin",
  "resource": "post-transcript",
  "type": "transcript",
  "url": "https://www.linkedin.com/posts/satyanadella_keeping-over-a-million-elevators-and-escalators-activity-7518982780551340032-z4go",
  "published_at": null,
  "collected_at": "2026-11-17T14:40:24.363764Z",
  "text": "TKL Rate is one of the leading companies in global infrastructure and mobility. ...",
  "language": null,
  "format": "plaintext",
  "duration_seconds": null
}

The fields:

  • id and url: the post the transcript belongs to. Use the URL as the join key back to your post data.
  • text: the transcript of the video's audio, taken from its captions.
  • language: the transcript language when available. It can be null, as in the example, so detect the language yourself if you route by it.
  • format: how the transcript is represented. The example is plaintext.
  • duration_seconds: the video duration when available.
  • collected_at: when SocQ collected the row.

The text comes from the captions attached to the video, so treat it with the same care as any caption: it may contain recognition errors, especially in names of people and companies. Quote it with a link to the post. Full schema: LinkedIn Video Transcript docs.

Fit It Into a LinkedIn Workflow

The transcript endpoint works on post URLs you already have. A typical pipeline:

  1. Find posts. Collect posts from the people or companies you follow with the LinkedIn Profile Posts API or LinkedIn Company Posts API.
  2. Select video posts. Keep the posts that contain a video.
  3. Fetch transcripts. Send those URLs to the LinkedIn Video Transcript API.
  4. Join and index. Join each transcript to its post by URL and index post text and transcript together for search, summarization or retrieval-augmented generation.

For a wider tour of profile, company, post and job data, see how to scrape LinkedIn with an API and the LinkedIn scraper API comparison. If you run the same pipeline for YouTube, the YouTube transcripts guide covers language handling and missing captions in more depth.

Use Cases

  • Executive and competitor monitoring. Turn what leaders say on video into searchable text alongside their written posts.
  • Content repurposing. Pull a talk or demo transcript as a draft for a blog post, newsletter or quote card, with the source link attached.
  • Sales and market research. Summarize product announcements and customer stories that only exist as video.
  • Archives and RAG. Store transcripts with the post URL and collected_at so every generated answer can cite its source.

Production Tips

  1. Deduplicate URLs. A post shared as a /posts/... link and as a /feed/update/urn:li:activity:... link carries the same activity ID. Normalize before submitting so you do not pay twice.
  2. Expect fewer rows than URLs. Only captioned videos return a row. Mark the others as having no transcript instead of retrying them.
  3. Keep the text as returned. Store the original text; do cleanup and chunking in a derived copy.
  4. Do not invent timestamps. The example format is plaintext. Cite the post, not a time position.

FAQ

What is the LinkedIn Video Transcript API?

A SocQ endpoint that takes LinkedIn post URLs containing a video and returns the words spoken in the video as plain text, from the captions attached to it.

Which URLs does it accept?

LinkedIn post URLs that contain a video, in the /posts/... or /feed/update/urn:li:activity:... form. Send several in the urls array.

Am I charged for videos without captions?

Billing follows the transcripts returned. Each captioned video returns one row and costs 0.7 credits ($0.0035); a URL that returns no row adds no per-transcript charge.

Does it transcribe the audio itself?

The transcript comes from the captions attached to the video. The documentation does not describe a speech-to-text fallback for videos without captions.

How much do 1,000 transcripts cost?

At 0.7 credits each, 1,000 transcripts cost 700 credits, or $3.50.

LINKEDIN API

Test the workflow with a public LinkedIn URL

Submit public inputs and receive normalized records with traceable source context.

Explore LinkedIn APIs