An ASO API for app import, keyword refreshes, and competitor workflows
The useful API path starts with real store data. Import an app, refresh keywords, discover competitors, then push the heavier work into crawl jobs when you want automation that survives beyond one script.
- ✦ Import real iOS and Android apps from one surface
- ✦ Queue heavier keyword refreshes instead of blocking clients
- ✦ Read crawl jobs, usage, and API keys from the same workspace model
- ✦ Use one workflow for dashboard, API, and MCP
Import and sync apps
Create a real app record from App Store search, Google Play search, a listing URL, or an app identifier, then refresh metadata when the store listing changes.
Refresh rankings and competitors
Track keywords, inspect live search results, discover competitors, and move heavier refresh work into crawl jobs when you want a stable automation path.
Operate the workflow
Monitor usage, manage API keys, check crawl-job status, and keep the operational side visible instead of guessing what the platform is doing.
First useful request
Import a real app before you automate anything else
The first good API experience is not a synthetic demo payload. It is finding a real app and making it reusable for metadata syncs, keyword refreshes, competitor discovery, and usage-aware automation.
curl -X POST https://apptide.xyz/api/v1/applications \
-H "Authorization: Bearer $APPTIDE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"search": "ChatGPT",
"platform": "ios",
"store": "app_store",
"country": "US",
"primaryLanguage": "en"
}'Stable resource shapes
Applications, keywords, competitors, snapshots, and jobs keep the same structure across the dashboard, API, and MCP.
Async where it matters
Small checks can stay live, but larger refreshes should queue cleanly so your scripts do not sit on slow store requests.
Observable by default
Usage, request logs, limits, and job history need to be visible before developers trust the API in real automation.
Copy-pasteable docs
A good API page should make first import and first refresh obvious before developers ever read about edge cases.
The API should feel like part of the product, not a sidecar
Use the dashboard for visibility
When you want quick answers, it should be obvious what the current app, keyword, and competitor state looks like.
Use the API for repeatable work
The same app import and refresh flow should be easy to move into scripts, internal tools, CI, and recurring jobs.