ASO.dev API: API for Developers and Partners

In Development  Coming Soon

Available only for the Pro and Marketing memberships.

We are preparing the ASO.dev API: a new capability many teams have been asking for.

The API is not meant for every ASO.dev user. We are building it for teams where ASO is already a recurring process: when data needs to flow into reports, internal systems, client workflows, BI, MCP, and AI scenarios.

For a long time, we were careful about selling data through an API.

Not because the API is unnecessary. It is necessary. Many teams have already outgrown manual exports, spreadsheets, and one-off reports. What we did not want was to turn ASO.dev into a raw data pipe with no context, no quality bar, no responsibility around usage, and no clear access model.

There is also a product reason. ASO.dev is built around seat-based monetization: the value is not only in the amount of data, but in how teams work with the product: analyzing apps, tracking positions, preparing reports, managing processes, and making decisions.

Now we are ready to build the API properly: not as a “download everything” switch, but as a careful product layer on top of ASO.dev, with clear methods, controlled access, credits for requests, and gradual expansion.

The API will be an add-on to ASO.dev, not a replacement for the subscription:

• an active ASO.dev subscription remains required
• seats remain the model for team access to the ASO.dev interface, projects, reports, and settings
• credits cover machine usage: requests, integrations, and automation
• each user will have their own API token for request authorization
• the API for developers is intended for internal team workflows
• the Partner API will be available only by separate agreement
• reselling data and building competing services are not allowed use cases
• during beta, terms, prices, limits, and methods may change

We are currently designing two API tracks:

• API for Developers - for developers, product teams, and ASO specialists who need to automate their own workflows.
• Partner API - for partners, agencies, services, and platforms that want to build integrations on top of ASO.dev.

Availability will open as the product is ready: first individual API methods, then a broader set of capabilities.

API for Developers is for teams that already use ASO.dev and want to automate repetitive work. It will be available as an add-on to an ASO.dev subscription, starting with the Pro plan.

Examples:

• retrieve app data
• fetch report results
• connect ASO.dev to internal BI systems
• run background operations from your own tools
• connect ASO.dev to MCP clients and AI agents
• send data into your own workflows

MCP is a separate scenario. Users already want to connect ASO.dev to AI tools so an agent can retrieve data, prepare reports, check apps, and help with recurring ASO tasks. The API will be the foundation for these integrations.

We want the API for developers to solve real tasks, not just formally repeat the product interface. Your scenarios matter now: what data you need, in what format, how often, and at which point in the workflow.

Partner API is intended for external integrations and partner scenarios.

It may be useful if you:

• run an agency or consulting service
• build an internal platform for clients
• want to add ASO.dev data to your product
• plan to connect ASO.dev to workflows, analytics, CRM, or reporting

Partner API requirements are usually different: access rights, stable contracts, clear limits, and integration support matter more. We treat this separately from the API for developers.

The Partner API is not bulk data access. It is a cooperation model between services, with an agreed use case, clear user value, and respect for the data source.

API access will use a user API token. Each user will have their own token for authorizing requests, and requests will consume the team’s credits.

Credits will be available in packages: larger packages will have a lower price per credit.

Packages will be available for:

• one month
• one year

The annual package is not about a lower credit price. It is about a longer validity period. It will be useful for smaller API volumes when you want purchased credits to last longer than one month.

Unused credits expire when the package period ends. Refunds for unused credits are not provided.

Exact prices, limits, and usage terms will come later.

We do not want to publish random numbers before we understand real load and the most important use cases.

We do not plan to release a huge API list at once.

The most requested methods will appear first in beta. Then we will expand the API as it becomes ready and as users send real requests. This approach is better for everyone:

• fewer unstable methods
• easier data quality control
• faster feedback
• clearer understanding of which scenarios matter
• lower risk of breaking integrations when things change

If you need a specific API method, email us. The more clearly you describe the scenario, the easier it is for us to understand priority, limits, and response format.

Useful details to include:

• what data or action you need
• which workflow you want to automate
• how often you expect to make requests
• which response format would be useful
• whether you need access only to your own apps or to multiple client accounts