Preview complete pages
Generate full-page images for review tools and internal website previews. Keep the target URL with the image so reviewers can identify its source.
Website Screenshot API
Website Screenshot API. Capture the page that matters.
Turn a URL into a PNG. Capture the whole page or focus on one element, then save the result alongside your workflow's data.
01 / OVERVIEW
What is Website Screenshot API?
AdsCrawl Screenshot API opens a URL in a browser and returns a PNG image through POST /screenshot. Use fullPage for a full-page capture or selector for the first matching element. The successful response is binary image data, so save it as a file rather than parsing it as JSON.
02 / USE CASES
Where it fits
Focus on a component
Capture a chart, card or other element with a precise CSS selector. The endpoint captures the first matching element.
Retain visual context
Store screenshots alongside monitoring results or research notes. A capture records the rendered page at request time; it is not a guarantee of future appearance.
03 / QUICKSTART
Start with one complete workflow
- Set a server-side API key and choose the target URL.
- Choose fullPage for the whole page or selector for one element.
- Send POST /screenshot with an appropriate documented wait condition.
- Check the response status and save the successful binary response as screenshot.png.
Requires Bash and cURL. Set the ADSCRAWL_API_KEY environment variable on your server first.
Full request and response reference →curl --fail-with-body -sS \
-X POST "https://api.adscrawl.net/screenshot" \
-H "x-api-key: $ADSCRAWL_API_KEY" \
-H "content-type: application/json" \
-d '{
"url": "https://www.adscrawl.net",
"fullPage": true,
"waitUntil": "load"
}' \
--output screenshot.png
# Add "selector": "main" to capture one element.- A failed response may contain error text instead of PNG bytes. Check the HTTP status before saving the output as an image.
- Lazy-loaded images and delayed widgets may require additional supported wait options. A load event does not guarantee all content is ready.
- Use a specific selector and confirm the element exists. The endpoint does not capture every matching element in one selector screenshot.
- Captures consume account credits and use browser capacity. Review pricing before scheduling frequent screenshots.
Keep API keys on the server. For HTTP 402 check your balance; for 429 reduce concurrency and retry with backoff.
05 / FAQ
Common questions
Can I screenshot only a chart?
Yes. Supply a CSS selector for the chart container. The capture uses the first matching element.
Does the screenshot endpoint extract text?
It returns PNG image data. For readable text, use the HTML or Markdown workflow; the screenshot endpoint is not an OCR service.
Why is some dynamic content absent?
The screenshot reflects the page when capture occurs. Check the target site's loading behavior and choose supported wait settings that match it.
