Isolate the API request
- Reproduce the same URL and options with a minimal API request.
- Compare the integration’s endpoint, JSON payload, and authentication headers with the working request.
- Check whether the integration expects a file, JSON URL, or base64 response.
- Record the SDK or integration version and the full error code.
Common integration mistakes
A JSON error body can be mistaken for an image if the HTTP status is ignored. A stored URL can be mistaken for the binary image itself. Authentication values belong in secret settings, not in published workflows or front-end code.
Request implementation help
Email a redacted request, language or automation platform, SDK version, expected output, and actual response. For CI failures, include the build identifier and whether the target deployment was reachable when the capture started.
Documentation
Related support articles
Fix an authentication or permission error
Troubleshoot missing keys, revoked credentials, and features your organization cannot use.
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.
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]