App Store Intelligence API: Keywords, Ranks & History

Get Appalize keyword metrics, market comparisons, stored rankings, history, modeled download estimates and app profiles. Eight App Store research operations; no customer API key required.

Data flow

Apify → api.appalize.com → Appalize services and stored research data. This Actor makes no direct Apple/iTunes requests and has no direct-store fallback. Appalize may maintain its data using Apple sources.

No Appalize account or API key is required from the customer. Publisher authentication is managed privately.

Quick start

{
  "operation": "keyword-metrics",
  "keywords": [
    "spotify"
  ],
  "apps": [
    "324684580"
  ],
  "countries": [
    "us"
  ],
  "maxReports": 2
}

Operations

keyword-metrics

One keyword × country. Returns stored measured popularity, modeled volume, difficulty, source, measurement time and stale flag. Missing data is not a zero score.

keyword-worldwide

One keyword × selected country group. Returns Appalize traffic/CI/KEI indices across up to 10 countries. These are modeled indices, not search counts; this source does not expose observation dates.

top-keywords

One country report with up to 100 stored keyword rows, ordered by the backend volume score. This is not a complete market demand census.

keyword-rankings

One keyword × country. Latest stored Appalize SERP positions, with observation time and up to 100 app rows. This does not initiate a new store scan.

rank-history

One keyword × Apple app ID × country. Up to 90 days of stored observations. Dates without data are omitted, never interpolated.

download-estimates

One Apple app ID × country. Modeled daily organic install contribution over up to 90 days of stored top-30 ranking history. Heuristic volume buckets × rank CTR; not measured downloads, sales or revenue. The underlying model uses a floor score of 5 when volume is unavailable.

app-profile

One Apple numeric app ID. Appalize public catalog profile; country is unknown and no country-specific live metadata claim is made. Any catalog estimates retain the source limitations.

tag-history

One Apple app ID × country. Existing tag snapshots within up to 90 days. Does not trigger a new capture. Empty tag lists do not prove the absence of Apple tags.

Output and cost

One dataset row is one successful report, including its nested rows. JSON preserves the complete nested data. Every report includes provider, operation, input, retrieval time and source provenance. Retrieval time is not the source measurement time.

Check the live Pricing tab for active prices. The result price is $20 per 1,000 reports, plus a $0.00005 Actor-start event (one per GB, minimum one), with platform usage included.

No-data responses are counted in RUN-SUMMARY and incur no report event. Failed API requests incur no report event. maxReports and Apify maximum-charge settings cap output costs. Shared upstream quotas may return 429; retries are bounded. If Appalize is unavailable, the run reports the failure rather than switching data sources.

Checkpoints skip completed units when resuming unchanged input. Dataset publication and checkpoint storage are not atomic; deduplicate recordId within a run after interruption.

Coverage and support

Data availability varies by keyword, country, app and date. We do not backfill missing history or fabricate zero demand. These products do not expose private App Store Connect sales, customer workspaces or advertising account records.

Built by Appalize. Report a run ID and non-sensitive input in Issues. Do not share authentication headers or secrets.