Example request
curl -X POST https://api.appscreenshotapi.com/v1/renders \
-H "Authorization: Bearer $APPSCREENSHOTAPI_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: ios-release-42" \
-d '{
"canvas": { "preset": "appstore.iphone_6_9" },
"preset": "aurora-midnight",
"slides": [
{
"headline": { "lines": ["Numbers you can", "act on"], "accent": "act on" },
"screenshot": { "url": "https://example.com/captures/home.png" }
}
],
"output": { "format": "fastlane_zip", "locales": ["en-US"] }
}'Not another drag-and-drop editor
The product path is code first: send a request from CI, a CLI, a release script, or an agent, then receive store-ready PNGs and a lint report.
AI is optional and BYOK. The final image render is deterministic and uses your real screenshots.
What the response gives you
Every render returns image URLs, exact dimensions, lint findings, and the number of screenshots consumed. Large matrices can run async with polling or signed callbacks.
FAQ
Can I generate App Store screenshots without opening an editor?
Yes. appscreenshotapi accepts JSON requests and screenshot URLs, then returns finished App Store screenshot images.
Does the API create fake app UI?
No. The renderer composites real captures you provide. Optional BYOK AI can draft copy and layout specs, but it does not generate the pixels of your app.