Skip to main content

Migrating from Direct Endpoints

Direct Endpoints under /api/v1 remain supported. For new focused data integrations, prefer the Unified API under /api/v2 so you get one request envelope, Workbench discovery, API key policies, usage logs, and provider-aware routing.

Quick map

Scrape

Direct Endpoint:
Unified API:

Search news

Direct Endpoint:
Unified API:

YouTube transcript

Direct Endpoint:
Unified API:

TikTok provider endpoint

TikTok profile data is provider-native, so use the provider endpoint lane:

Media extraction

Use extract_audio or extract_video for focused media extraction:

Still use Direct Endpoints for these

Keep using /api/v1 when you need current Make.com compatibility, PDF utility endpoints, AI image generation, agent completion, JS/Python execution, or LinkedIn endpoints.