AppPage.net - app websites & store data

Search Google Play or App Store apps by keyword (live results). Returns app ids, titles, developers, ratings and prices, each with an apppage_url page that has full details. Use get_app for details of one app.

Get details of one app. For Android pass the package name (e.g. com.whatsapp): developer with the contact email and website they publish on Google Play, category, rating and rating count, installs, price, in-app purchases, ads, version, size, required Android version, content rating, release and last-update dates, summary, description and recent changes. For iPhone/iPad pass the numeric App Store id (e.g. 310633997): the same kind of details plus required iOS version, star histogram and languages.

List apps similar to a given app (the store's similar-apps list), compared by rating, price, installs (Android) and last update. Use for questions like "apps like X" or "alternatives to X".

List Google Play or App Store top charts (live results): top free, top paid or top grossing apps, overall or in a category. Google Play categories look like game_puzzle or health_and_fitness; App Store categories look like games_puzzle or photo_and_video.

Get user reviews of an app: star rating, date, text and app version; on Google Play also helpful votes and the developer's reply, on the App Store a review title. Use it to summarize what users like or complain about.

Get an app's privacy information. Android: the Google Play data safety section (data shared with third parties, data collected and why, security practices, privacy policy link) and the Android permissions it requests, grouped by type. iPhone/iPad: Apple's App Privacy labels (data used to track you, data linked to you, data not linked to you) with data categories and purposes.

List the apps published by one developer. Google Play: by developer name as returned by other tools (e.g. "Wikimedia Foundation"). App Store: by developer_id from get_app or search_apps with store=app_store (a developer name also works; it is looked up by search).

List the AppPage.net sites in your account: address, app, store, theme and which pages and app-ads.txt are filled in.

Takes no parameters.

Details of one of your sites: its app, theme, page URLs, whether each page is filled in, and its app-ads.txt records.

Check whether {subdomain}.apppage.net is free for a new site. 3-14 lowercase letters, digits or hyphens.

Create a website for a published app at {subdomain}.apppage.net, filled from its store listing (name, icon, screenshots, description, store buttons). Its privacy policy, terms, account deletion and support pages start empty: write them with set_page. Check the address with check_subdomain first.

Change the design (theme) of one of your sites.

Read the current HTML of one of your site's pages: privacy_policy, terms, delete_account or support.

Make one of your site's pages from AppPage.net's templates, the same ones as its privacy policy, terms, account deletion and support page generators: fixed, store-ready English text where each answer turns whole sections on or off. The app's name, developer, contact email (Google Play), website, platform, collected data types, ads, in-app purchases, version and the store's FAQ come from the store listing; your answers override them. Prefer this to writing a page yourself with set_page. Ask the user what the listing can't tell (SDKs, accounts, children, where they're based) before generating. save=false returns the page as Markdown without saving.

Replace one of your site's pages with new content: the privacy policy, terms and conditions, account deletion instructions (both stores ask for this page when an app has accounts) or support page with an FAQ. Write it in Markdown (default) or HTML; scripts, forms and event handlers are removed. Base it on what the app really does and collects (get_app_privacy shows its store privacy data), and include a contact email.

Write the app-ads.txt file served at https://{subdomain}.apppage.net/app-ads.txt, which ad networks (AdMob and others) check against the developer website in the store listing. One record per line: ad system domain, publisher account id, DIRECT or RESELLER, optional certification id, e.g. "google.com, pub-1234567890123456, DIRECT, f08c47fec0942fa0". The lines are checked first; nothing is saved if any has an error. mode=append adds only the records that aren't there yet.

Re-read the site's app from Google Play or the App Store now (name, icon, screenshots, description, what's new). Fields the store sends empty keep their current value. Once a minute per site.

Which extras one of your sites has turned on (feedback board, bug reports, beta sign-up, promo codes, remote config, changelog, press kit, status page) with their URLs, its remote config, open status incidents, the latest changelog entries and its App Links files.

Turn one of your site's extras on or off: feedback (feature request board), reports (bug report form), beta (beta tester sign-up), promo (promo code page), remote_config (app-config.json for force updates, maintenance and notices), changelog, press (press kit) or status (status page). Their settings are kept.

Add a release to your site's public changelog (and its RSS feed). Give version and notes, or from_store=true to add the store listing's current version and What's new. Turns the changelog on if it's off.

Post an incident on your site's status page, e.g. an outage or planned maintenance. Turns the status page on if it's off. Apps reading app-config.json can show it too.

Mark an incident on your site's status page as resolved. get_modules lists the open incidents and their ids.

Change the remote config your app reads from https://{site}/app-config.json: the lowest supported and latest versions per platform (apps below the lowest must update), the update message, maintenance mode and an in-app notice. Only the fields you pass change; pass "" to clear one. Turns remote config on.

Read what users sent through your site: feature requests on the feedback board (with votes and status) or bug reports (message, app version, OS and device; without the sender's email).

Write the files that let links to your site open your app: Apple's apple-app-site-association (Universal Links) and Android's assetlinks.json (App Links), served under https://{site}/.well-known/. Give ios_app_ids (TEAMID.bundle.id) and android_package with android_sha256 fingerprints, and they are built for you; or pass a whole file as apple_json / android_json. A platform you leave out keeps its file.

Your AppPage.net plan (Free or Pro), what it includes and how much of today's API limit is used.

Takes no parameters.

Serve one of your sites on your own domain, such as www.myapp.com (Pro). Returns the DNS record to add; the domain works once the record is in place and the certificate is issued. Call it again with the same domain to check progress.