Use case

Docs and changelogs

Take the pictures in your documentation on every release, from the pipeline, so they are never a version behind the thing they document.

The problem
Documentation screenshots rot silently. Nobody notices that the button moved three releases ago until a customer does, and re-taking them by hand is exactly the chore that gets skipped.
What we do about it
One call per image in CI, against your staging URL, with the same parameters every time. Commit what comes back, or serve it from us.

The call

A domain-restricted API key means the token in your CI can only ever be pointed at your own hosts.

bash
curl -X POST https://webshotter.com/api/v1/webshots \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://staging.example.com/dashboard", "preset": "macbook-air", "hide_selectors": ".intercom-launcher, #cookie-banner"}' \
  -o webshot.png

Other use cases

Screenshots of your own product, from CI

Free to start, no card, and one endpoint to learn. The first webshot takes about a minute.