Authentication
Every request to https://api.scrapier.io/api/v2 must carry your API key in the X-API-Key header:
curl "https://api.scrapier.io/api/v2/me" \ -H "X-API-Key: YOUR_API_KEY"Get a key
Section titled “Get a key”Create and revoke keys at app.scrapier.io/dashboard/api-keys. Keys start with sk_live_.
Header only
Section titled “Header only”- The REST API reads the key only from the
X-API-Keyheader. - Keys in the query string or the request body are ignored.
- Bearer tokens in the
Authorizationheader are not accepted by the REST API. They work only with the MCP server.
When the key is wrong
Section titled “When the key is wrong”| Status | When | Body |
|---|---|---|
401 |
The X-API-Key header is missing. |
{"error": "Missing HTTP_X_API_KEY header."} |
403 |
The key is unknown or invalid. | {"detail": "Authentication service unavailable or invalid API key."} |
403 |
The key was revoked. | {"detail": "API key has been revoked."} |
These bodies have no success field, and the 403 uses detail rather than error. Read the message from error ?? detail. Details in Errors.
Check a key at any time with the free GET /me endpoint.
If a key leaks
Section titled “If a key leaks”Revoke it in the dashboard and create a new one. Revoked keys get 403 straight away.