appXL documentation
Getting an app running on appXL takes three steps: connect the store account so the agent can read your listing and metadata history, confirm the markets and competitors it should watch, and set who approves changes before they ship. From there the agent works on a standing cycle — research, draft, propose, measure — and everything it produces is readable over the API. This page is the orientation map; each area below links to the detailed reference.
Key takeaways
- Connection is read-only until you explicitly grant publish permission.
- Approvals are per app, and can be routed through a queue on Scale plans.
- Every artefact the agent produces is available over the REST API and via webhooks.
- Rate limits and API versions are returned on every response, so pin the version in your client.
Getting started
- 1
Connect your store accounts
Authorise App Store Connect and Google Play Console with read access. The agent uses this to pull your listing, your metadata history and your performance metrics.
- 2
Confirm markets and competitors
Select the storefronts you publish in and confirm the competitor set. The agent proposes a starting set from your category; you edit it.
- 3
Set your approval model
Choose who can approve a metadata change. Nothing reaches a live listing without an approval, regardless of plan.
- 4
Run the first audit
The agent scores the current listing field by field and produces its first set of proposed changes, usually within an hour of connection.
Reference areas
| Area | Covers | Where |
|---|---|---|
| Connection | Store authorisation, permissions, revocation | In-app setup guide |
| Workflow | Audit cycle, proposals, approvals, rollback | In-app workflow guide |
| API | REST endpoints, auth, pagination, versioning | /product/api |
| Webhooks | Regression alerts, competitor changes, completed audits | /product/api |
| Data definitions | How volume, difficulty and position are derived | /aso/aso-kpis-ranking-factors |
| Terminology | Every ASO term the product uses | /aso/glossary |
Permissions and safety
Store connections start read-only. Publish permission is granted separately and per app, and can be revoked without breaking the read-side integration or losing history.
Every published change is recorded with the approver, the timestamp and the previous value, so any change can be traced and reverted to its prior state.
Frequently asked questions
Does appXL need write access to App Store Connect?
Not to start. Connections are read-only until you explicitly grant publish permission for a specific app, and that permission can be revoked at any time.
How long does the first audit take?
Usually under an hour after the store connection completes, depending on how much metadata and review history there is to read.
Is there an API?
Yes — an authenticated REST API with cursor pagination and webhooks. The endpoint reference is on the API product page.
appXL Research
App Store Optimization Research Team
The appXL research team analyzes App Store and Google Play ranking data across the apps our agent manages, and publishes what it finds.