/app-data

ASO API for app-store intelligence

View examples Talk to sales

Illustrative App Data API fields

Example Run · running tracker

example.com

Illustrative rank: 4 · rating: 4.7

App listing metadata

example.com

Category: Health & Fitness

App Store Optimization

example.com

Research Apple App Store and Google Play results, listings, charts and reviews. Compare visibility by app identifier, keyword, store and country.

Example Run · running tracker

example.com

Illustrative rank: 4 · rating: 4.7

App listing metadata

example.com

Category: Health & Fitness

Workflows

Illustrative workflows built with search data

Workflows

Illustrative workflows built with search data

App Data API capabilities

Research Apple App Store and Google Play results for a keyword, store and market. Retain positions and app identifiers with each observation.

Running shoes — research example

             example.com
            

Ask which question you need to answer first. Then select the data family, fields, and collection cadence that support that decision.

Results

Inspect app metadata, category and rating context. Keep store-specific field definitions instead of assuming every field has the same meaning across stores.

Running shoes — organic result

             example.com
            

Example ranking: 1 · United States · desktop · organic result.

Trail running shoes — category page

             example.com
            

Research supported Apple App Store and Google Play listings, search results and reviews. Keep the store, country and app identifier attached to every observation.

Running guide — informational page

             example.com
            

Use comparable inputs for repeated research. Inspect the source context before interpreting a change as a trend.

Example Brand — citation research

             example.com
            

Plan API requests for individual tasks or discuss a bulk dataset when your analysis needs a broader historical view.

Highlights

Collect supported lists and chart positions to investigate category visibility. Record the chart, country and collection date for meaningful comparisons.

Structured data for your workflow

              "content"
             
              : {
             
              "
              
              keyword
              
              "
             
              :
             
              Illustrative App Data API 
              
              fields
             
              "
              
              Compare keyword visibility, listing content, and review patterns in supported stores.
              
              "
             
              :
             
              "
              
              organic
              
              "
             
              example.com
             
              "
              
              location
              
              "
             
              :
             
              "
              
              United States
              
              "
             
              example.com
             
              "
              
              Inspect app store search results and rankings for relevant terms.
              
              "
             
              :
             
              "
              
              desktop
              
              "
             
              }

Structured outputs

Use supported app-listing search and filters to build a research segment. Validate relevance before comparing apps with different categories or audiences.

Structured data for your workflow

Compare available app metadata, categories, and product positioning. 1 The demo records are illustrative. Discuss production access, request volume, and collection cadence with the DataSEO team. 2 3 App rankings, listings, metadata, ratings, and reviews for App Store Optimization and competitor research. 4 .

AI Summary

Read review text, ratings and dates alongside app IDs. Preserve sorting and retrieval depth so repeated collections remain comparable.

Illustrative response fields

Connect app data with Labs app metrics, keywords, competitors and intersections. Distinguish store visibility from estimates of demand or business performance.

Queued collection 69.6% / 454ms

Live collection 67.8% / ~1.2s

SEO Labs 80.0% / 4.3s avg

Sample collection 46.0% / 2.7s

Sample collection 41.0% / 1.3s

Example collection 43.0% / 547ms

Sample collection 50.0% / 583ms

Accuracy / Latency

Example app intelligence

Accuracy / Latency

Example coverage (%)

30%

40%

50%

60%

70%

80%

90%

Queued collection 69.6% / 454ms

Live collection 67.8% / ~1.2s

SEO Labs 80.0% / 4.3s avg

Sample collection 46.0% / 2.7s

Sample collection 41.0% / 1.3s

Example collection 43.0% / 547ms

Sample collection 50.0% / 583ms

300ms 500ms 1s 2s 4s

Latency (ms, log scale)

Pricing

Collection scope and access

Request a quote for your volume

View examples Talk to sales

batch Queued

Scheduled data collection

live Live

Store the market, keyword, source ID and observation time. Repeat the same collection to investigate listing changes rather than promising a complete historical app database.

extended Extended

Confirm the selected route and source

FROM IDEA TO FIRST REQUEST

Build with App Data API

An app can have different metadata and visibility across stores and countries. Set those inputs explicitly before comparing search positions.

Read the docs ↗Talk to our team ↗

NODE.JS

// Server-side example; configure your deployment and credentials.
const url = new URL("/v3/app_data/apple/app_searches/task_post", process.env.DATASEO_API_ORIGIN);
const auth = Buffer.from(`${process.env.DATASEO_LOGIN}:${process.env.DATASEO_PASSWORD}`).toString("base64");
const response = await fetch(url, {
  method: "POST",
  headers: {Authorization: `Basic ${auth}`, "Content-Type": "application/json"},
  body: JSON.stringify([{"keyword": "running tracker", "location_code": 2840, "language_code": "en", "depth": 10}])
});
if (!response.ok) throw new Error(`HTTP ${response.status}`);
const data = await response.json();
for (const task of data.tasks ?? []) {
  if (task.status_code !== 20000) throw new Error(task.status_message);
}
// Use task.result only after checking task status.

Browse the complete API endpoint reference