Integrations

App Store Connect & RevenueCat

Automate App Store Connect with your Issuer ID, Key ID, and .p8 — and query RevenueCat charts with your secret key. Appeeky proxies both; vendor secrets are not stored. Send them per request next to your X-API-Key.

Apple ASC API

RevenueCat Charts API

When to use which

Public App Store intelligence (search, keywords, estimates) uses only the Appeeky key. Connect and RevenueCat routes are for your products — metadata edits, ASC analytics, sales reports, and subscription metrics from RevenueCat.

GET /v1/connect/apps

↓

versions · localizations · analytics · sales

App Store Connect

List apps and versions, update metadata localizations, request analytics reports, download Sales & Trends, respond to reviews — /v1/connect/…

X-API-Key: <appeeky>
X-ASC-Issuer-Id: <uuid>
X-ASC-Key-Id: <key id>
X-ASC-Private-Key: <pem>

RevenueCat

Overview and time-series charts (MRR, revenue, churn, trials) — /v1/revenuecat/overview, /v1/revenuecat/charts/…. Plan limits follow RevenueCat.

X-API-Key: <appeeky>
X-RC-Key: <sk_…>

Same dashboard key for Appeeky; add ASC or RevenueCat headers only on the routes that need them.