# Transcript Dock Video Transcripts (`transcriptdock/transcriptdock-video-transcripts`) Actor

Get transcripts from YouTube and TikTok captions, or use paid AI transcription for Instagram Reels in beta. Bring your Transcript Dock API key. Returns full text, timed segments, job status and billing. Apify compute usage is separate.

- **URL**: https://apify.com/transcriptdock/transcriptdock-video-transcripts.md
- **Developed by:** [Transcript Dock](https://apify.com/transcriptdock) (community)
- **Features:** Limited permissions
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Transcript Dock Video Transcripts

Get timed transcripts from public YouTube and TikTok videos through the Transcript Dock API. Instagram Reels use AI transcription on paid Transcript Dock plans in beta.

Use your own Transcript Dock API key. Our website is available on the [Transcript Dock developer profile](https://apify.com/transcriptdock). Your key is a secret input encrypted by Apify. It is sent only to the fixed Transcript Dock API origin and is never written to the dataset or logs. Each user's key selects their own workspace; there is no shared billing account.

### Input and cost

Enter up to 50 HTTPS video links. Duplicate links are removed before submission. Captions only is the default and costs 1 Transcript Dock credit per video. Selecting auto explicitly permits AI fallback; transcribe always requests AI. AI costs 2 credits per started minute and requires a paid Transcript Dock plan. Instagram requires auto or transcribe mode.

`maxCredits` caps each video, default 10 credits. The maximum run spend is the cap multiplied by the number of unique links. Apify compute usage is separate. Check your available Transcript Dock credits and Apify allowance before running. This Actor has no additional rental or result fee configured.

`timeoutSeconds` limits waiting per video, default 300 seconds. Jobs can continue on Transcript Dock after waiting ends. The output preserves their actual status and job ID so you can retrieve them later. The Actor does not cancel or silently resubmit them.

Example input with placeholders. Replace both the key and video URL before running:

```json
{
  "apiKey": "REPLACE_WITH_YOUR_TRANSCRIPT_DOCK_KEY",
  "urls": ["PASTE_YOUR_PUBLIC_VIDEO_URL_HERE"],
  "mode": "captions_only",
  "maxCredits": 10,
  "timeoutSeconds": 300
}
```

Uploads, direct media URLs, translation and speaker labels are not Actor input options. Unsupported fields are rejected before any submission.

### Output and recovery

The Apify dataset contains one row per unique URL, with `jobId`, actual `status`, `timedOut`, billing information and the full JSON transcript when it succeeds. Transcript text, segments, language and timing come from the real API response. Failed jobs carry a typed error; pending jobs carry no invented transcript. Apify can export dataset rows as JSON or CSV.

The Actor stores completed progress in its run's private key value store. It reuses the same submission receipt when the same Apify run resumes, and retries transient errors at most three times. The server's receipt retention window is at least 24 hours; recovery after that window is not guaranteed to avoid another charge. A new Apify run uses new receipts, with normal Transcript Dock content cache rules.

Dataset writes and progress checkpoints are separate operations. An interruption between them can repeat a row on recovery. Deduplicate output by `jobId`. Changing input or credentials during the same run is rejected. API authentication or transport failures stop the run rather than producing success rows.

### Local setup and checks

Requires Node 22.15 or later. Run from the standalone Actor repository root, or from `integrations/apify` in the application monorepo:

```sh
npm ci --ignore-scripts
npm test
docker build -t transcriptdock-apify:local .
```

Local tests use clearly separated fixtures and make no paid API calls. The container runs as a nonroot user with writable local storage. Dependencies are pinned and recorded in `package-lock.json`. Security overrides pin patched MCP SDK, Zod, FTP parser and glob matcher versions inherited from the upstream packages; local tests exercise the resulting client and lifecycle.

The SDK loads platform input and decrypts secret fields automatically. For local development, follow the Apify SDK's secret input instructions; never commit a real key in a local `storage/` directory or input file. Credentials must have `jobs:write`, `jobs:read` and `transcripts:read` scopes.

### Release evidence

Local tests cover retry receipt reuse and caps, pending and failed jobs, redirect credential protection, checkpoint recovery, account isolation and error redaction. The Apify CLI input schema validator passes. On 2026-11-02, the Transcript Dock organization completed a real cloud build and a captions_only run with a 1 credit cap. The run succeeded with one dataset row containing a full transcript; the API reported a cached result and zero Transcript Dock credits charged. The run used limited permissions. Live AI transcription and paid source paths were not tested in this check. Apify compute usage is separate from Transcript Dock credits.

For support, open the Actor's [Issues tab](https://apify.com/transcriptdock/transcriptdock-video-transcripts/issues).

# Actor input Schema

## `apiKey` (type: `string`):

Your key from Transcript Dock. It is stored encrypted by Apify.

## `urls` (type: `array`):

Up to 50 public YouTube, TikTok or Instagram Reel links.

## `mode` (type: `string`):

AI requires a paid Transcript Dock plan. Instagram needs auto or transcribe mode.

## `maxCredits` (type: `integer`):

Maximum Transcript Dock credits for each video. Multiply by your link count for the run cap.

## `timeoutSeconds` (type: `integer`):

When the wait ends, the output includes the current job status and ID. The job may still finish later.

## Actor input object example

```json
{
  "mode": "captions_only",
  "maxCredits": 10,
  "timeoutSeconds": 300
}
```

# Actor output Schema

## `results` (type: `string`):

One result per unique video link, including job status, billing and the full transcript when available.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("transcriptdock/transcriptdock-video-transcripts").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("transcriptdock/transcriptdock-video-transcripts").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call transcriptdock/transcriptdock-video-transcripts --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,transcriptdock/transcriptdock-video-transcripts"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/XPyfHR4ntccEGagtw/builds/p9yPUoXJ1VRc7iQNa/openapi.json
