API Overview
The Scraper API allows you to integrate social media data from Twitter and YouTube into your applications. This documentation provides everything you need to implement our API quickly and efficiently.
Base URL
All API requests should be made to the following base URL:
Request Format
All requests should include:
- Your API key in the
X-API-Keyheader - For public keys, origin validation headers (
OriginandReferer) - Content-Type:
application/jsonfor POST requests
Authentication
Scraper API uses API keys for authentication. We offer two types of keys:
- Private Keys (
sk_*) - For server-side applications - Public Keys (
pk_*) - For client-side applications (with origin validation)
Learn more about authentication →
Credit System
Our API uses a credit-based system for access control:
- Each request consumes 1 credit from your account
- Monitor your usage in your Scraper dashboard
- Purchase additional credits as needed for your application
Response Format
All API responses are in JSON format with a consistent structure:
Success Response
Error Response
Status Codes
The API uses standard HTTP status codes:
200- Success401- Unauthorized (invalid API key)402- Payment Required (insufficient credits)404- Not Found500- Server Error
Available Endpoints
Twitter Data
Access Twitter user information and content:
- User Details - Profile information
- User Followers - Follower data
- User Tweets - User's tweet history
- Single Tweet - Specific tweet details
YouTube Data
Access YouTube channel information and content:
- Channel Details - Channel information
- Channel Shorts - Shorts video data
- Single Short - Specific short details