Feb 4

Public API

Hi Astro team,I’d like to submit a feature request regarding automation and integrations.I actively use Astro for keyword research and tracking, and I’d love to have access to a public API that would allow:- Programmatic access to keyword search and metrics- Fetching rankings and historical data- Generating or retrieving weekly reports- Automating keyword discovery and monitoring workflowsMy use case is building internal automation (e.g. scheduled weekly reports, custom dashboards, and keyword analysis pipelines). Right now, this kind of automation isn’t possible without manual work, which limits how deeply Astro can be integrated into existing workflows.Even a first version of the API (read-only, rate-limited, or available on higher plans) would already unlock a lot of value for power users and teams.If this is something on your roadmap, I’d be happy to share more details about my use cases or participate in beta testing.Thanks for the great product and looking forward to your thoughts.

Reviewing

Feb 4, 2026

Hi Pavel, thanks for the feedback! We could consider something similar, but it would be a completely different product from Astro, geared more towards teams and companies. May I ask how much you would be willing to pay for access to a similar service? These are the prices of apptweak: https://www.apptweak.com/en/pricing#api

Feb 7, 2026

Hi Matteo, thanks for the reply — that’s a really tough question. AppTweak’s entry API plan starts at $166/month, which is honestly very expensive for an indie developer. That said, it includes 250,000 credits, and if we roughly assume 1 credit = 1 API request, the per-request cost comes out to about $0.000664, which actually feels quite reasonable. Because of that, I think the main issue isn’t the unit economics, but the high fixed monthly commitment. Personally, I’d be much more comfortable with a pay-as-you-go model, similar to what HikerAPI does: https://hikerapi.com/pricing Something usage-based (possibly with a small minimum or developer tier) would make it accessible for indie developers and small teams, while still scaling well for larger companies. Hope this perspective helps — happy to share more concrete usage numbers or scenarios if that’s useful.

Feb 11, 2026

Thank you very much for your reply! I think we need more data, so perhaps I could conduct a survey among our users. The key issue is how many users are willing to pay for this feature because, from our point of view, it requires a considerable amount of effort to manage; it's like having a second product.