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
| Direct Endpoint | Unified API target | Notes |
|---|---|---|
POST /api/v1/scrape | capability:scrape_page | Best default for new page scraping jobs. |
POST /api/v1/crawl | capability:crawl_site | Use for crawl jobs with a simple site-level contract. |
POST /api/v1/search-news | capability:search_news | Use for recent-news discovery. |
POST /api/v1/get-youtube-transcript | capability:get_youtube_transcript | Use for normalized transcript output and provider fallback. |
POST /api/v1/get-tiktok-profile | endpoint:scrapecreators.tiktok_profile | Provider-native TikTok data stays in the provider endpoint lane. |
POST /api/v1/extract-audio | capability:extract_audio | Use for audio summarization or structured audio extraction. |
POST /api/v1/extract-video | capability:extract_video | Use for video summarization or structured video extraction. |
Scrape
Direct Endpoint:Search news
Direct Endpoint:YouTube transcript
Direct Endpoint:TikTok provider endpoint
TikTok profile data is provider-native, so use the provider endpoint lane:Media extraction
Useextract_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.