What does the AppScreens screenshot API create?

The AppScreens REST API creates and updates editable App Store and Google Play screenshot projects, manages approved assets and copy, renders previews and exports, and can continue into separately approved metadata, draft-release and screenshot-delivery workflows.

How does the Developer API authenticate?

REST, CI and scripts use a scoped AppScreens API key in the Authorization Bearer header. API keys are coming soon. Store yours in a secret or environment variable, and never place it in chat, source control or browser code. MCP clients use browser-based OAuth when supported.

Can I generate iOS and Android store screenshots with an API?

The API renders saved designs for the iPhone, iPad and Android targets enabled for the account. Select the pages, languages and targets, inspect the real preview and retrieve completed PNG or JPEG exports.

Can I keep editing the same project in AppScreens?

Yes. The API and visual editor use the same saved project. Save and close the editor before an API write, then reopen the updated project for visual adjustments. Revision checks reject a write if the project changed in the meantime.

Does the API capture my running app?

Your simulator, UI tests or capture tool supplies the app images. AppScreens places those captures in an editable screenshot design, adds the captions and device treatments, and renders the finished store assets.

Is this a website screenshot API?

No. The AppScreens Developer API automates AppScreens screenshot projects: it turns your app captures and an editable design into App Store and Google Play screenshots. It doesn’t capture websites from a URL.

Can I automate localized screenshots?

Yes. Supply reviewed translations from your script, translation service or AI workflow. The API and MCP service apply your wording and locale-specific captures, then render the enabled languages and targets. Inside the AppScreens editor, built-in translation tools are also available.

Can I use the API with Fastlane or GitHub Actions?

Yes. Call the REST API from a script or CI job with a scoped key, follow the durable export operation and download its finished archives. Fastlane snapshot or screengrab can supply app captures; AppScreens creates the designed assets; deliver or supply can handle your chosen upload path.

Does an export upload my screenshots to Apple or Google?

An export produces files and can prepare a store-ready archive. Direct AppScreens store delivery is a separate workflow with a destination preview and confirmation, so creating the assets never silently changes a store listing.

How do I automate App Store screenshots for iOS and Android?

Capture your app UI, create or select an AppScreens project, then update the captions and images for your release. Preview the selected iPhone, iPad and Android outputs, export the finished files and continue into your store-delivery workflow.

How is this different from the App Store Connect screenshot API?

Apple’s API manages screenshot sets and uploads in App Store Connect. AppScreens creates the designed images first, combining your captures, captions, layouts and device frames. Separate approved tools can also manage supported metadata, create an Apple version or Google draft release and deliver screenshots. They do not upload binaries, attach builds, submit, publish or start a rollout.

Is the Developer API available now?

Public API access is not open yet. The API is in private testing. Build and save the reusable screenshot project in AppScreens now.

What plan includes API access?

Pricing will be announced when public access opens.

How is the API different from Agent MCP?

Use REST with scoped API keys for explicit HTTP operations in scripts, applications and CI. Use the hosted MCP connection with browser-based OAuth for a compatible AI agent. Both interfaces call the same underlying AppScreens services.

Developer APIComing soon

One workflow
Both stores

App Store Screenshot API

Coming soon: ship updated App Store and Google Play screenshots without rebuilding the design. The AppScreens REST API will update your captures and captions, render previews and export PNG or JPEG assets for the devices and languages you choose.

Design your screenshot project

See the release scope

Public access is not open yet. Build the reusable project in AppScreens today, ready for the API. Agent MCP

A saved SnackCart screenshot project in the AppScreens editor

200K+app professionals use AppScreens

199,950 +

App professionals

Screenshots exported

≈0

Developer days saved

As recommended by teams on

Editable designs, automated updates

Keep your screenshot design. Automate the next release.

Save your screenshot design

Update an editable AppScreens project

Start with an AppScreens template or reuse a project you already designed. Your script replaces the captures and captions that changed, while the layout, branding and device treatments stay editable in AppScreens.

CookBook recipe search screenshot designed in AppScreens

CookBook meal-planning screenshot designed in AppScreens

CookBook recipe import screenshot designed in AppScreens

Generate your release assets

One request. Every selected size and language.

Choose the screenshot pages, languages and device sizes once. AppScreens renders the combinations on the server, so your script can check progress and collect the finished files when they are ready.

POST /v1/previews

{
  "projectId": "<saved project ID>",
  "screenshotIds": ["<screenshot page ID>"],
  "languageCodes": ["en-US", "de-DE"],
  "targetIds": ["<enabled render target ID>"],
  "format": "jpeg",
  "scale": 0.25
}

See a complete request

Your development stack

Fits your release workflow

REST + OpenAPI: One documented contract for REST and MCP
Any HTTP client: curl, Node, Python or your own tools
GitHub Actions: Keep the files with your release
Fastlane: Hand off to deliver and supply

Seven release steps

Automate App Store screenshots for every release

Keep the design you approved. Your script updates the parts that changed, previews them and exports the store sizes you need.

The OpenAPI reference and connection guide are coming soon.

Jump to the request example

1
Connect and check the account
Use a scoped API key, then read account readiness, enabled capabilities and the separate API and render allowance before starting work.
- GET /v1/account/setup
- GET /v1/capabilities
- GET /v1/usage
2
Set up the app and destination
Create or select the AppScreens app record, validate its identifiers and use the secure browser handoff when store credentials are needed.
- POST /v1/apps
- POST /v1/apps/{id}:validate
- POST /v1/store-lifecycle/credentials/setup
3
Choose the project, languages and targets
Browse templates, create or duplicate an editable project, then configure the supported languages and store output targets for the release.
- GET /v1/catalog/templates
- POST /v1/projects
- PATCH /v1/projects/{id}/settings
4
Apply approved assets, copy and design changes
Upload and validate app captures, plan their assignments, update reviewed text or translations and apply supported design-document changes against the current revision.
- POST /v1/assets/uploads
- POST /v1/projects/{id}/text:replace
- POST /v1/projects/{id}/design-document:import
5
Validate and inspect the real preview
Catch missing assets before export, then render the selected pages, languages and devices. Review a page or contact sheet before generating the full set.
- POST /v1/projects/{id}/export:validate
- POST /v1/previews
- GET /v1/operations/{id}:wait
6
Export and retrieve the finished files
Start the full-resolution export, wait or poll without holding one request open, then request a fresh short-lived link for the owned files.
- POST /v1/exports
- GET /v1/operations/{id}:wait
- GET /v1/exports/{id}/files/{fileId}/download
7
Continue into separately approved store work
Read shared metadata guidance, preview listing or draft-release changes, and separately approve screenshot delivery to the exact reviewed app, store and languages.
- POST /v1/apps/{id}/store/metadata/preview
- POST /v1/apps/{id}/store/releases/preview
- POST /v1/store-lifecycle/deployments/preview

Capabilities

What the API covers

Create and update an editable project, render its screenshots and collect the finished assets from your own tools. The API also supports store metadata and screenshot delivery, with approval before store changes.

Scroll across to see every column.

Developer API capabilities compared with the AppScreens editor
Operation	AppScreens editor	Developer API
Create or duplicate a project from a template or blank canvas	Available now	Included
Configure languages, targets and project settings	Available now	Included
Replace app captures for each device and language	Available now	Included
Update captions, translations and supported design settings	Available now	Included
Preview pages, devices and languages	Available now in Preview & Export	Included
Export PNG or JPEG files and retrieve shared history	Available now	Included
Inspect versions and restore an earlier project revision	Included in testing	Included
Manage metadata, draft releases and approved screenshot delivery	Store workflows available now	Included

Automate localized screenshots from one project

Keep translated captions, local app captures and device sizes in the same project. Your script supplies the wording for each market; AppScreens applies it to the design and renders the combinations you select.

Three screenshot pages across two languages and three device targets make 18 images, rendered from one saved design.

Build your localized screenshot project

CookBook’s English meal-planning screenshot

Your repository → AppScreens → Fastlane

Automate app screenshots with Fastlane and GitHub Actions

Keep snapshot, screengrab or your UI tests for capturing the app. Add AppScreens where those raw captures become designed, localized store screenshots.

Keep your AppScreens key in an Actions secret, never in the repository.
Stable idempotency keys make retried jobs safe.
Keep the files and operation ID with your build artifacts.

Fastlane screenshot capture →GitHub Actions secrets →AppScreens and Fastlane guide →

Store-ready archives

Example structure

App Store

fastlane/
└── screenshots/
    ├── en-US/
    └── de-DE/

fastlane deliver

Google Play

fastlane/metadata/android/
├── en-US/images/
│   └── phoneScreenshots/
└── de-DE/images/
    └── phoneScreenshots/

fastlane supply

An export can prepare an archive in Fastlane’s folder layout for one store. Packaging the files does not upload them; store upload stays a separate step with your own credentials, or AppScreens’ direct uploads.

Apple delivery →Google Play delivery →Direct uploads →

Create an editable screenshot project by API

Choose the design you want to keep using. The API creates an editable project from the template, ready for your app captures and approved captions. Server and CI requests use a scoped AppScreens API key, and creation jobs use stable idempotency keys for safe retries.

Create a project

POST /v1/projects HTTP/1.1
Host: api.appscreens.com
Authorization: Bearer <APPSCREENS_API_KEY>
Content-Type: application/json
Idempotency-Key: <unique-key-for-this-request>

{
  "mode": "template",
  "templateId": "<selected template ID>",
  "name": "Next app release",
  "clearTemplateScreenshots": true
}

API endpoints

GET /v1/capabilitiesRead the actions enabled for the account and connection.
GET /v1/usageCheck API and render allowance before starting work.
GET /v1/catalog/templatesBrowse reusable starting designs.
GET /v1/projects/{projectId}Read the project, its settings and current revision.
POST /v1/assets/uploadsCreate a constrained upload for an owned image asset.
POST /v1/projects/{projectId}/export:validateRun the shared design and export-selection checks.
POST /v1/previewsRender selected pages, languages and output targets for inspection.
POST /v1/exportsStart the full-resolution render operation.
GET /v1/operations/{operationId}:waitWait briefly or return the latest durable operation state.
GET /v1/exports/{exportId}/files/{fileId}/downloadIssue a fresh short-lived link for an owned completed export.

Before, during and after each run

Release screenshots within your existing pipeline

Choose what your integration can do

Give each connection the access it needs. Revoke an integration without losing the screenshot projects it helped create.

Keep the latest design intact

If a designer changes the project while your script is running, the API refuses to overwrite that newer work.

Keep exports running in the background

Start a render and check back for the result. The server continues working without your script holding a request open.

Plan around your remaining allowance

Check API and render usage before a large batch, so your workflow knows how much work it can start.

Return to a design that worked

Restore a saved project version and continue from there, in your script or the visual editor.

Catch missing assets before export

Check the selected design, images and outputs before rendering the release files. Resolve issues before they reach your store upload.

REST for scripts. MCP for agent conversations.

Use the API for explicit HTTP steps in your application, scripts or CI. Agent MCP lets an AI agent work through the same project tasks with you.

Explore Agent MCP

Build the project now. Connect the pipeline next.

Prepare the editable screenshot set in AppScreens today. Public API pricing will be announced with availability.

Start your editable project

Start with a design you can see

Build and review the reusable project in the visual editor. Use the same design for your API workflow.

Create a screenshot project

We've Boosted Downloads for over 200,000 App Developers

Real feedback from app builders shipping faster and looking sharper on the App Store and Google Play.

Jean RFounder @ The Daily Gain

“It has helped us save countless hours, meet store standardized dimensions and elevate the quality of our screenshots.”

Fernando Mvia Email

“It is really easy to make a good set of screenshots. Amazing tool! Loved it”

@frankomyg via X

“Looks like I have some preview screens! Thanks again to @AppScreens. Pretty good at handling different devices (iOS/Android) with multiple languages”

Chris O via AppSumo 5 out of 5

“Well worth the money, saves hours and hours of kicking around. Highly recommend!”

Jean RFounder @ The Daily Gain

“It has helped us save countless hours, meet store standardized dimensions and elevate the quality of our screenshots.”

Fernando Mvia Email

“It is really easy to make a good set of screenshots. Amazing tool! Loved it”

@frankomyg via X

“Looks like I have some preview screens! Thanks again to @AppScreens. Pretty good at handling different devices (iOS/Android) with multiple languages”

Chris O via AppSumo 5 out of 5

“Well worth the money, saves hours and hours of kicking around. Highly recommend!”

@MuseumShuffle via X

“Thanks again for making such a nice tool available to devs. As someone who knows nothing about design or design tools, this was *fantastic* to use to generate my App Store screenshots.”

Treeger via AppSumo 5 out of 5

“You can focus on creating pretty screenshots & polishing marketing phrases. Truly an awesome product!”

@danwegner via X

“AppScreens is making me sooooo happy!”

Jax C via Product Hunt

“I don't think I could release my app without this tool. It single handedly creates all the output sizes I need to release my app to the Apple App Store and Google Play Store, from one design.”

@MuseumShuffle via X

“Thanks again for making such a nice tool available to devs. As someone who knows nothing about design or design tools, this was *fantastic* to use to generate my App Store screenshots.”

Treeger via AppSumo 5 out of 5

“You can focus on creating pretty screenshots & polishing marketing phrases. Truly an awesome product!”

@danwegner via X

“AppScreens is making me sooooo happy!”

Jax C via Product Hunt

“I don't think I could release my app without this tool. It single handedly creates all the output sizes I need to release my app to the Apple App Store and Google Play Store, from one design.”

Jaime MFounder @ Dowin

“Great for indie devs or small teams! It's super easy to use and saves you a lot of time, all without compromising design flexibility.”

Jonas A via Product Hunt

“Perfect for generating promotion images for App Store! Perfect to auto translate and manage multiple translations and variations”

Sri via AppSumo 5 out of 5

“The thing I love about this tool is that you can export the screenshots to fit all device sizes in one single click.”

Jaime MFounder @ Dowin

“Great for indie devs or small teams! It's super easy to use and saves you a lot of time, all without compromising design flexibility.”

Jonas A via Product Hunt

“Perfect for generating promotion images for App Store! Perfect to auto translate and manage multiple translations and variations”

Sri via AppSumo 5 out of 5

“The thing I love about this tool is that you can export the screenshots to fit all device sizes in one single click.”

5.0 from AppSumo reviews 5.0 from Product Hunt reviews

One workspace

AppScreens is a browser-based App Store and Google Play screenshot designer: one editable project exports every required iPhone, iPad and Android size in 80+ languages and uploads to App Store Connect and Google Play Console.

Create

Optimize

Manage & automate

FAQs