Authentication
Connect your backend securely with a ScrapingBuddy API key.
Create and store a key
Create a key from Profile > API access while signed in. Store it in an environment variable such as SCRAPINGBUDDY_API_KEY. Use your deployment platform secret store in production.
API keys identify your account. Never include them in browser JavaScript, screenshots, uploaded challenges or support messages. If a key is exposed, revoke it in your account and replace it.
Authenticate every request
Send the key in the Authorization header using the Bearer scheme. Both POST and GET requests need this header. Do not put your key in a query string.
For task creation, also send Content-Type: application/json and a UUID v4 Idempotency-Key. GET polling does not require an idempotency header.
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Idempotency-Key: 11111111-1111-4111-8111-111111111111Use the customer API
All examples use the public customer API base URL below. Append /captcha/tasks to create or list tasks and /captcha/tasks/{id} to fetch one.
The dashboard uses separate internal routes. Do not copy those routes into your integration; use /api/v1. Your ScrapingBuddy key cannot be substituted with a 2Captcha key.
https://www.scrapingbuddy.com/api/v1