Stores & identifiers
The Data API supports Apple App Store and Google Play. Use the following identifiers wherever an endpoint path contains :store:
| API identifier | Store | App ID format |
|---|---|---|
itunes_connect |
Apple App Store | Numeric App Store ID, such as 553834731. |
google_play |
Google Play | Package ID, such as com.king.candycrushsaga. |
App Store identifiers
Section titled “App Store identifiers”Apple App Store apps use the numeric ID from their store URL. For example, Candy Crush Saga’s URL ends in id553834731, so its API ID is 553834731.
App Store publishers also have public numeric IDs. King’s publisher ID, for example, is 526656015.
Google Play identifiers
Section titled “Google Play identifiers”Google Play apps use the package ID from the store URL’s id query parameter. For Candy Crush Saga, use com.king.candycrushsaga.
Apptopia uses internal numeric IDs for Google Play publishers and for SDKs in both stores. Use the identifier returned by the corresponding metadata or discovery endpoint.
IDs in JSON responses
Section titled “IDs in JSON responses”The JSON type of an ID can vary by endpoint. App metadata lookups and app/publisher measurement lookups return id as a string. Publisher metadata IDs are integers. Apple App Store app IDs and publisher IDs can also be integers in discovery, search, charts, and bulk exports. Google Play app IDs remain package-name strings.
Preserve the returned value when parsing a response, and normalize IDs consistently before joining records from different endpoints. A quoted numeric ID and its integer representation can identify the same entity. See each attribute page for endpoint-specific differences.
Metadata fields can be absent or null when information is unavailable. Store-specific fields and nested contact data also vary by record.
Combined datasets
Section titled “Combined datasets”The custom reports endpoint also accepts unified for reports that combine Apple App Store and Google Play data. Use it only when your report does not require a particular store. See Custom data reports.
The parent_company_general_data bulk export uses unified because parent companies span both stores. See Bulk data exports.