1
Submit
POST your brand term to create_store_search_request. It returns a request id.2
Poll
GET get_store_search_request/{id} with the id from the previous step. Repeat until status reports the search has finished.3
Read
GET list_store_search_result, passing the request id as searchrequest, and page through the matching apps.Request parameters
Submit (create_store_search_request):
Read (
list_store_search_result):
Both
create_store_search_request and list_store_search_result cost 0 credits. Submit is throttled at 100 requests/day; poll and read are each throttled at 500 requests/day.
What comes back
The poll endpoint returns the request object. Watch itsstatus field to know when the search is done:
id— the request ID you poll and pass assearchrequest.search_term— the term you submitted.create_date/update_date— when the request was created and last updated.status— the search state; read results once it reports finished.is_monitoring,alert_cycle,is_email,is_reporting,report_id— monitoring and reporting flags for the request.follow_up_token— token tying this search to its tracking record.
id— result ID.name— the app’s listed name.store— which store it was found in (for exampleitunesorgoogle_play).link— direct URL to the store listing.searchrequest— the request ID this result belongs to.appeared_date— the date the app was first seen.updated_at— when the record was last updated. FormattedDD/MM/YYYY, HH:MM:SS(nullable) — not ISO 8601.
link for each result and confirm whether the listing is genuinely yours. For confirmed impersonators, file a takedown with the store and watch appeared_date to gauge how long the spoofed app has been live and exposing your customers.