Check API authentication
- Send the full API key in the
X-API-Keyheader. - Check for extra spaces, surrounding quotes accidentally included in the value, or an empty environment variable.
- Confirm the key has not been revoked and belongs to the intended organization.
- Verify your integration sends the header to
https://api.allscreenshots.com, rather than to a documentation or dashboard URL.
Distinguish permissions from credentials
A 401 indicates that authentication needs attention. A 403 can indicate permissions, an unavailable capability, or a blocked URL. Read the error code and message before replacing a working key. Feature availability is shown in the dashboard and depends on the organization’s plan and enabled features.
Report a persistent error
Include the endpoint, HTTP status, error code, request ID, UTC timestamp, organization name, and a redacted request. Never include the full API key.
Documentation
Related support articles
Fix a request validation error
Use supported options, valid JSON, and the correct capture endpoint.
Understand rate limits and quota errors
Separate temporary request throttling from a used-up screenshot allowance.
Use async jobs for longer captures
Submit a job, check its status, and download the result only after completion.
Need help with this issue?
Email support with this article, your request or capture ID, and the result you expected. Remove credentials and private information first.
Email [email protected]