AppListingLab API

Screenshots and ASO copy, from a store URL

A small REST API that turns an App Store or Google Play link into store-ready screenshots and copy. Authenticate with an API key, and drive everything through three endpoints.

1 · Onboard an app

POST a store URL. We read the listing and return an appId to generate against.

2 · Submit a job

Ask for a screenshot set — device, count, narrative. It runs as a background job.

3 · Poll the job

Poll the jobId until it's done, then read the finished screenshot set.

The whole loop

Here is the entire flow in three calls — onboard an app, request a set, and poll until it's ready. Everything is scoped to your API key and metered in credits.

cURL

# 1 · onboard an app from its store URL
curl -s https://api.applistinglab.com/api/v1/public/v1/apps \
  -H "Authorization: Bearer $APP_LISTING_LAB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"iosUrl":"https://apps.apple.com/app/id1234567890"}'
# → { "appId": "665f…", "name": "Your App", ... }

# 2 · request a screenshot set (returns a jobId)
curl -s https://api.applistinglab.com/api/v1/public/v1/screenshots \
  -H "Authorization: Bearer $APP_LISTING_LAB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"appId":"665f…","device":"iphone-67","count":5}'
# → { "jobId": "77a1…", "credits": { "cost": 5, "remaining": 95 } }

# 3 · poll until status is "succeeded"
curl -s https://api.applistinglab.com/api/v1/public/v1/jobs/77a1… \
  -H "Authorization: Bearer $APP_LISTING_LAB_API_KEY"
# → { "id": "77a1…", "status": "succeeded", "result": { ... } }

Keep reading

Quickstart

From an API key to your first screenshot set in about a minute.

Authentication

Create keys, send them safely, and rotate when needed.

Generate screenshots

Onboard an app, submit a job, and poll it to completion.

API reference

Every public endpoint, its parameters, and example responses.

Errors & credits

Status codes, the credit model, and how limits are enforced.