Look up entities
Use entity lookups when you already know the IDs of the records you need. Each request accepts one id or repeated id[] values, up to 50 IDs.
Endpoints
Section titled “Endpoints”| Method | Route | Reference |
|---|---|---|
GET |
/api/:store/app |
App metadata |
GET |
/api/:store/app_versions |
Version history |
GET |
/api/:store/publisher |
Publishers |
GET |
/api/parent_company |
Parent companies |
GET |
/api/:store/sdk |
SDKs |
GET |
/api/:store/app_sdks |
Installed SDKs |
GET |
/api/:store/app_files |
App file data |
GET |
/api/:store/app_tags |
App tags |
For advertising declaration files, see App ads.txt and Publisher ads.txt.
Specify IDs
Section titled “Specify IDs”- One entity:
id=389801252. - Multiple entities:
id[]=479516146&id[]=525818842. - App Store apps use numeric store IDs. Google Play apps use package IDs such as
com.instagram.android. - Publishers and SDKs use their own identifiers. An app ID cannot be substituted for a publisher or SDK ID.
In the playground, change the id parameter name to id[] and add another id[] row to request multiple records. All three generated code examples preserve repeated query keys.
Read the response
Section titled “Read the response”Responses contain a JSON array of matching documents. Fields depend on the selected endpoint. For example, a publisher response includes an id, name, and app_ids:
[ { "id": 479516146, "name": "Mojang", "app_ids": [479516143] }, { "id": 525818842, "name": "Ndemic Creations", "app_ids": [1124500826, 525818839] }]This example is abbreviated. See the linked attribute pages for the full set of documented fields.