API Documentation

Introduction

Welcome to the Scrape Creators API documentation. Our comprehensive REST API provides powerful endpoints to extract public data from 38+ social media platforms including TikTok, TikTok Shop, Instagram, YouTube, Rumble, and more.

🚀 Quick Start Guide

Get started in minutes with our free API key. Extract profile data, posts, videos, and more from any public social media account.

API Authentication

All API requests require authentication using an API key. You'll need to include your API key in the x-api-key header with every request to our REST API endpoints.

🔑Don't have an API key? Get one by signing up at app.scrapecreators.com

⚡No Rate Limits

Scrape Creators does not enforce API rate limits. For now, we recommend keeping usage below 500 concurrent requeststo ensure the best performance and reliability.

Key Features of Our API

🚀 High Performance

Fast, reliable API responses with 99.9% uptime and enterprise-grade infrastructure.

📊 Real-time Data

Extract the latest public data from social media platforms in real-time.

🔧 Developer Friendly

RESTful API with comprehensive documentation and code examples in 6+ languages.

🔒 Secure & Compliant

Only public data extraction with enterprise security and privacy compliance.

Integrations

Use Scrape Creators from AI agents, workflow tools, cloud actors, or your terminal.

MCP

Model Context Protocol server for AI-powered social media scraping in Cursor, Claude, VS Code, and more.

Agent Skill

Teach AI coding agents best practices for using ScrapeCreators APIs across 27+ social platforms.

CLI

Scrape 27+ social media platforms from the terminal. 110+ endpoints, one command.

npm

Machine Payments

Let AI agents buy credit packs on their own over HTTP 402 with the Machine Payments Protocol (MPP), paying via Stripe.

n8n

Open-source workflow automation tool with Scrape Creators community node.

Apify

Cloud platform for web scraping and automation with ready-to-use Scrape Creators actors.

Using the Documentation

LLM-Ready Prompts

Simply click the sparkles icon and paste the generated prompt into ChatGPT, Claude, or your favorite AI assistant to get instant help with implementation. You can also send agents straight to llms.txt or the full LLM docs.

💡Response Field Explanations

This section is to help you understand some of the fields returned by the social media platform.

🔍JSON Path Navigation

In fullscreen mode, hover over any JSON key to see its complete path. Right-click to copy either the full path or just the key name - perfect for navigating complex response structures.

Response Codes

Our API uses conventional HTTP response codes to indicate success or failure:

  • 200Success
  • 400Bad Request - Invalid parameters or missing required fields
  • 401Unauthorized - Invalid or missing API key
  • 402Payment Required - Gotta purchase more credits
  • 403Forbidden - The public source blocks this resource, such as an age-restricted YouTube video behind an age check
  • 404Not Found - We could not find the requested resource
  • 500Server Error - Please try again later

Response-contract changelog

HTTP status codes, response fields and types, error values, message values, and credit behavior are part of the API contract, including responses for missing, private, and restricted resources. We preserve those contracts on existing endpoint versions. Incompatible changes require an explicitly versioned contract and advance notice, not a silent change during a scraper fix.

October 18, 2026 — Instagram profile access responses

This retrospective note records the original changes below and the deliberate success-flag correction noted afterward. Instagram profile recovery work on October 12–15 changed which error responses some requests receive. We should have announced the contract changes before they shipped. Sorry for the disruption.

  • Confirmed age gates on /v1/instagram/profile initially returned HTTP 403, success: false, error: forbidden, errorStatus: 403, age_restricted: true, and message: Profile is age restricted, with zero credits charged. Some of these requests previously returned HTTP 200 with error: not_found, errorStatus: 404, and message: Profile is restricted; others reached an upstream 500. The older restricted placeholder still exists.
  • Explicit audience restrictions return an uncharged HTTP 404 with error: not_found and message: Profile is restricted. Confirmed unavailable pages return an uncharged HTTP 404 with message: Profile is unavailable on Instagram. Neither response establishes an age/region reason or proves deletion.
  • The older HTTP-200 private, restricted, and missing-account placeholders still exist and cost one credit. Their JSON errorStatus: 404 is not the HTTP status. The Account doesn't exist message was not renamed globally: unavailable-page confirmation is a separate response path. The current metadata-first pipeline also no longer infers a restriction from an empty timeline alone: it preserves matching metadata as a partial HTTP 200. The older restricted-result handler remains for compatibility.
  • /v1/instagram/user/posts and /v2/instagram/user/posts also have explicit uncharged age-gate 403 and restricted/unavailable 404 responses. Their age-gate bodies do not include age_restricted. Their explicit restricted-profile 404 says Profile is private. This note does not change /v1/instagram/post or /v1/tiktok/profile.

Apart from the success-flag correction below, the current status codes, fields, messages, and credit behavior are retained. See the exact examples and GET/POST differences on the Instagram Profile and Instagram Posts pages.

October 19, 2026 — confirmed profile states are successful lookups

Confirmed profile age gates (HTTP 403) and restricted/unavailable profiles (HTTP 404) return success: true on /v1/instagram/profile, /v1/instagram/user/posts, and /v2/instagram/user/posts. This corrects the success: false value introduced by the resource-state error paths. A confirmed state is a completed lookup, not a scraping failure. Only that boolean changes: HTTP status, exact error/message values, field presence, and zero-credit billing remain unchanged. Actual scraping failures still return success: false.

Support & Feedback

If you encounter any issues, have feature requests, or find bugs in the API or documentation, please email me at support@scrapecreators.com