Changelog

Every change to the Prisma reviews API, newest first: new platforms, new endpoints, and changes in the Google, Trustpilot, App Store and Google Play APIs that affect your integration. Within v1 changes are additive (new endpoints, optional parameters, response fields and event types), so write your client to ignore fields it doesn’t know. The one exception so far is the 2026-10-26 entry, which removed reply drafts before they had customers; it says what to change.

2026-10-26 · Changed: Replies by API on 5 platforms, read only on 6

Prisma connects APIs: it reads reviews and publishes the reply text you send (written by you, your software or your own model) through the platform’s official API. It doesn’t write replies or keep unpublished ones.

• Replies by API on Google Business Profile, App Store, Google Play, Judge.me and Trustpilot (beta). POST /v1/reviews/{id}/reply returns 202 with reply.status: "queued", then published (or failed).
• Read only on Yelp, Tripadvisor, Booking.com, Yotpo, REVIEWS.io and G2 (beta, Beam and up). These platforms have no reply API for third parties. Prisma reads their reviews, and each review’s url links to where you answer it on the platform (for some platforms, the listing or product page).
• New error 422 reply_not_supported for POST and DELETE /v1/reviews/{id}/reply on read-only platforms, with the extra fields platform and url. See Errors.
• Reply statuses are now published, queued and failed. There is no draft status.
• GET /v1/usage no longer returns the ai_drafts field. Reply drafts, listed as not available yet in v1, won’t ship, and plans don’t include them.

Action needed: if you sent replies for Yelp, Tripadvisor, Booking.com, Yotpo, REVIEWS.io or G2 reviews, handle 422 reply_not_supported and send users to the review’s url. Stop reading ai_drafts from /v1/usage. Details on Replies and Platforms.

2026-10-23 · New: Accounts and dashboard

Early access is over: anyone can create an account and start building.

• Sign up with your email and a password (we send a link to confirm your email), or with Google, GitHub or Apple. Then sign in at any time.
• Your workspace starts on the free Spark plan, with a live key (pk_live_…) and a test key (pk_test_…). The dashboard shows both in full once; after that, only their prefix. The test key works right away with sample data.
• Roll a key from the dashboard to replace it: the new key is shown once and the old one stops working at once. This is also how you revoke a key you think was exposed.
• The dashboard shows your plan, your keys, your usage and your connections.
• Paid plans can’t be bought from the dashboard yet. To move to Beam, Spectrum or Aurora, email hello@prismareviews.com.

Action needed: none. Start with the Quickstart once your keys are in the dashboard.

2026-10-23 · New: Prisma API v1

The first version of the API is available at https://api.prismareviews.com/v1 for every workspace, with live keys (pk_live_…) and test keys (pk_test_…). Test keys work with every platform on sample data and never touch a real account.

Platforms. Eleven platforms, each with a live connector:

• Replies by the platform’s official API: Google Business Profile (OAuth), App Store (App Store Connect API key), Google Play (Prisma’s service account invited in Play Console), Judge.me (shop domain and private token) and Trustpilot (OAuth, beta).
• Replies as drafts the owner publishes: Yelp, Tripadvisor and Booking.com (public listing URL), Yotpo, REVIEWS.io and G2 (API credentials). All in beta.

How each one connects, with the exact fields, is on Platforms.

Endpoints.

• Reviews: GET /v1/reviews (filters location_id, platform, since, has_reply; cursor pagination, up to 100 per page) and GET /v1/reviews/{id}.
• Replies: POST /v1/reviews/{id}/reply (create or replace, with Idempotency-Key) and DELETE /v1/reviews/{id}/reply.
• Locations: GET /v1/locations, GET /v1/locations/{id}.
• Connections: POST /v1/connections (OAuth, credentials or listing URL), GET /v1/connections, DELETE /v1/connections/{id}.
• Webhooks: POST /v1/webhooks, GET /v1/webhooks, DELETE /v1/webhooks/{id}, with the events review.created, review.updated, reply.published, reply.failed and connection.updated, signed with Prisma-Signature (HMAC-SHA256).
• Usage: GET /v1/usage.

Limits you should know about.

• Reply length is checked before queueing: Google Business Profile 4,096 bytes, App Store 5,970 characters, Google Play 350 characters (422 reply_too_long).
• Google Play and Judge.me can’t delete replies through their APIs (422 operation_not_supported), and Judge.me can’t edit them either.
• The Google Play API only returns reviews from the last 7 days; Prisma keeps the history from the day you connect. See Google Play reply-to-reviews documentation.
• Google limits edits per Business Profile (see Google Business Profile API usage limits). Replies are queued and retried.
• Per-key rate limits by plan: Spark 60, Beam 120, Spectrum 600 and Aurora 1,200 requests per minute.

Not available yet: SDKs, an OpenAPI spec and AI reply drafts. They will appear here when they ship.

Action needed: none. Start with the Quickstart, then the API reference and Errors. Platform guides: Google Business Profile API, Google Play reviews API, Yelp, Tripadvisor.