Developers
Your reviews and replies, on a clean REST API.
Pull every app and review into your own tools, or subscribe a webhook and react the moment a review lands, a reply publishes, or a rating drops. Read-only, workspace scoped, and signed.
Pro plan and up·read-only·signed webhooks
01 / Endpoints
Two reads, everything you need.
A small, stable surface. List your apps, then page your reviews with a cursor. Each review carries its reply, so one call gives you the whole conversation.
GET/api/v1/apps
Every app in your workspace: name, publisher, platforms, current rating and review total. A stable public subset, never internal fields.
GET/api/v1/reviews
Your reviews, newest first, each with its reply embedded. Filter by app, page with a keyset cursor, and pull the whole history without offset drift.
# List your apps curl https://www.replyargus.com/api/v1/apps \ -H "Authorization: Bearer ra_live_..." # Page your reviews, newest first curl "https://www.replyargus.com/api/v1/reviews?limit=50" \ -H "Authorization: Bearer ra_live_..."
02 / Webhooks
Events, pushed to you and signed.
Point a webhook at your own endpoint and Argus posts these events as JSON, each with an HMAC signature you can verify. Connect a channel in Integrations to turn any of them on.
review.created
A new review landed on one of your apps.
draft.created
Argus drafted a reply that is waiting for approval.
reply.published
A reply went live on the store.
digest.weekly
The weekly rollup for an app is ready.
anomaly.detected
A rating drop or review spike tripped an alert.
test
A ping you can fire yourself to verify your endpoint.
03 / Keys
Read-only keys, scoped to your workspace.
Minted in the app
An admin generates a key in Settings under Developers. The raw value is shown once, then only its prefix. Revoke anytime.
Scoped and read-only
A key sees only its own workspace and can only read. It never publishes, never edits, and never crosses into another org's data.
Predictable JSON
Stable public fields, keyset pagination with a next_cursor, and per-key rate limits. No surprise schema, no offset drift.
From the blog
Build against the API
We wrote down what the App Store and Google Play APIs actually document, and what breaks when you build against them. Free, sourced, and useful whether or not you ever use Reply Argus.
Character limits, edit and delete, permissions, publication delay. Quoted from the vendor, or marked undocumented.
Read →UNAUTHENTICATED, permissionDenied, projectNotLinked, and why reviews.list comes back empty.
Read →One 401 body for six mistakes, the 20-minute token rule, and the RSS feed that hides throttling behind a 200.
Read →API FAQ
The review API, answered.
Endpoints, keys, webhooks, and limits for pulling your reviews and replies into your own stack.
Get an API keyWhat can the API do?
It is read-only. You can list your apps and pull your reviews, each with the reply Argus drafted or published. For real-time events, subscribe a webhook and receive review, draft, publish, digest and anomaly notifications as JSON.
How do I authenticate?
Send an API key as a bearer token. Keys are read-only, scoped to your workspace, and generated in Settings under Developers. An admin mints the key and the raw value is shown once.
Are webhooks signed?
Yes. Every webhook POST carries an HMAC signature header derived from a per-endpoint secret, so you can verify the payload came from Reply Argus and was not tampered with. The secret is revealable to admins in the connect flow.
Which plan includes the API?
Pro and up. Reads are keyset-paginated and rate-limited per key. The API and webhooks are additive to everything else your plan already includes.
Built to be trusted with your data
The protections behind every review we read and every reply we draft.
Encrypted, and yours alone
Your store credentials are encrypted at rest and in transit. We never see your raw keys.
Isolated per workspace
Reviews, replies, and knowledge are isolated at the database layer. One workspace can never read another's.
We never store card data
Payments run through a merchant of record. Card details never touch our servers.
Scoped, revocable access
Role-based permissions, OAuth for integrations, and hashed API keys you can revoke anytime.
Nothing ships without your say-so
Drafts never publish on their own. Auto-publish is an explicit opt-in, off by default.
Hardened by default
Strict security headers, a content security policy, enforced HTTPS, and signed, verified webhooks.
Wire your reviews into everything else.
Start free, then unlock the API on Pro. Read-only keys, signed webhooks, no card to begin.
API on Pro · $79/mo · cancel anytime