Example request
curl -X POST https://api.appscreenshotapi.com/v1/renders \ -H "Authorization: Bearer $APPSCREENSHOTAPI_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: release-42-screenshots" \ --data @store-screenshots.json
Reference table
| Input | Output | Why it matters |
|---|---|---|
| Real app captures | Framed store screenshots | The UI stays truthful; the layout becomes repeatable |
| Canvas presets | Apple-sized PNGs | No manual dimension lookup in CI |
| Locale list | Per-locale screenshot sets | One release job can cover multiple markets |
| Idempotency-Key | Safe retries | Build agents can retry without duplicate billing |
API-first by design
The durable artifact is not a Figma file or browser editor state. It is a JSON request that can live in a repo, be edited by an agent, and be rerun whenever the app changes.
Typical render lifecycle
Capture real screens, send the render request, inspect lint findings, download the images or Fastlane ZIP, then hand the result to human review before store upload.
FAQ
Can the API generate all App Store device sizes?
Yes. Send the target canvases and locales in the output request; each final exported image counts as one screenshot.