The appXL ASO API
The appXL API exposes the same keyword, ranking, metadata-history and review data the agent works from, over authenticated REST endpoints returning JSON. It exists so ASO data does not stay trapped in a dashboard: teams pipe it into a warehouse to join against revenue, into BI tools for their own reporting, or into internal workflows that trigger on a ranking regression. Access is scoped per key, rate limited per plan, and every response is versioned so integrations do not break when the schema evolves.
What it does
Keyword and ranking endpoints
Read tracked keyword sets, difficulty and volume estimates, and daily sampled positions by storefront, device and language.
Metadata history
Every recorded change to your listing and your tracked competitors' listings, timestamped so movement can be attributed to a release.
Reviews and ratings
Review text, ratings distribution and clustered themes, so support and product tooling can consume the same signal the agent uses.
Webhooks
Subscribe to regression alerts, competitor metadata changes and completed audits instead of polling for them.
What the agent handles for you
- Keeps the underlying data fresh so integrations read current state, not a stale export.
- Emits webhooks when a tracked position or competitor listing changes materially.
- Annotates ranking records with the metadata change that preceded them.
- Rate limits and scopes keys automatically per integration.
How the API is shaped
| Resource | Returns | Common use |
|---|---|---|
| /keywords | Tracked terms, volume, difficulty | Warehouse sync, planning sheets |
| /rankings | Sampled positions by storefront | Internal dashboards, alerting |
| /metadata | Listing change history | Release attribution |
| /reviews | Reviews, ratings, themes | Support routing, product feedback |
| /audits | Completed audit results | Reporting to stakeholders |
Integration patterns that work
- Nightly warehouse sync: pull rankings and keywords once a day and join against install and revenue tables.
- Alerting: subscribe to regression webhooks and route them into your incident channel rather than polling.
- Reporting: pull audit results on a monthly cadence to generate stakeholder reports in your own template.
- Workflow triggers: fire a task in your tracker when a competitor changes their title or subtitle.
Authentication and limits
Requests authenticate with a bearer key issued per integration and scoped to the resources that integration needs. Keys are revocable individually, so rotating a warehouse credential never interrupts your alerting.
Rate limits are set per plan and returned on every response, and endpoints that can return large result sets are cursor-paginated. Responses carry an explicit version so a schema change never silently breaks a client.
Frequently asked questions
What format does the API return?
JSON over authenticated HTTPS REST endpoints, with cursor pagination on collection resources and an explicit version on every response.
Can competitor data be pulled through the API?
Yes, for the competitors you track: their metadata history and their positions on your tracked keyword set are both available.
Are there webhooks, or is it polling only?
Both. Webhooks cover ranking regressions, competitor metadata changes and completed audits; everything else is available on request.