Platforms

Prisma reads reviews from eleven platforms and returns them in the same JSON. This page lists, for each one, the platform ID, how it connects with POST /v1/connections, whether Prisma can publish replies there and how often Prisma checks for new reviews.

Summary

• By API: Prisma publishes the reply through the platform’s official API (202, status: "queued", then published).
• Read only: the platform has no reply API for third parties. Prisma reads the reviews, and each review’s url links to where you answer it on the platform (for some platforms, the listing or product page). POST and DELETE /v1/reviews/{id}/reply return 422 reply_not_supported. Prisma never logs into a customer’s account.
• — in the limit column means Prisma’s own limit of 10,000 characters applies.
• Connecting a platform that isn’t in your plan returns 403 plan_upgrade_required. Plans are on Pricing.

How often Prisma checks for reviews

The first sync starts as soon as a location is connected. After that:

last_synced_at and next_sync_at on each location show the schedule, and review.created webhooks fire when a new review is found. The first sync imports up to 90 days of history on Spark, 365 days on Beam and everything the platform returns on Spectrum and Aurora.

Google Business Profile

"platform": "google" · OAuth · replies by API · Google Business Profile API

{ "platform": "google", "redirect_url": "https://yourapp.com/prisma/callback" }

• The owner or a manager of the profile approves access on Google’s consent screen (scope business.manage). Prisma imports every location that account can see, one location per Business Profile location.
• Prisma uses its own Google Cloud project, so you don’t need one.
• Replies: up to 4,096 bytes; posting again replaces the reply; deleting is supported.
• Google limits edits per profile (see Google Business Profile API usage limits). Prisma queues replies and retries when Google answers with 429.

App Store

"platform": "app_store" · credentials · replies by API · App Store reviews API

Create an App Store Connect API key with the Customer Support role (App Store Connect → Users and Access → Integrations) and send:

{
  "platform": "app_store",
  "credentials": {
    "issuer_id": "57246542-96fe-1a63-e053-0824d011072a",
    "key_id": "2X9R4HXF34",
    "private_key": "-----BEGIN PRIVATE KEY-----\nMIGTAgEAMBMG...\n-----END PRIVATE KEY-----"
  }
}

Each app the key can see becomes a location (address holds the bundle ID). Replies: up to 5,970 characters; posting again replaces the reply; deleting is supported. Apple applies hourly limits per key (see App Store Connect API rate limits).

Google Play

"platform": "google_play" · credentials · replies by API · Google Play reviews API

In Play Console, invite Prisma’s service account, reviews@sopa-reviews-play.iam.gserviceaccount.com, with the permissions Reply to reviews and View app information, for the apps you want to connect. Then send their package names:

{ "platform": "google_play", "credentials": { "package_names": ["com.example.app"] } }

Prisma checks access to every package when you connect, so a typo or a missing invitation returns 422 invalid_credentials at once. Each package becomes a location.

• The Google Play API only returns reviews created or edited in the last 7 days. Older reviews aren’t available, so your history is what Prisma has stored since you connected.
• Replies: up to 350 characters; posting again replaces the reply; Google Play’s API can’t delete replies (422 operation_not_supported). See Google Play reply-to-reviews limits.

Judge.me

"platform": "judge_me" · credentials · replies by API · Judge.me reviews API

One location per shop, with all its product and store reviews. Judge.me’s API can create replies but can’t edit or delete them: send each reply once (DELETE returns 422 operation_not_supported). Its API doesn’t return replies written elsewhere, so reply only shows replies sent through Prisma.

Trustpilot (beta)

"platform": "trustpilot" · OAuth plus credentials · replies by API · Trustpilot API

Trustpilot’s OAuth doesn’t say which profile the user manages, so send the profile’s domain with the request:

{
  "platform": "trustpilot",
  "redirect_url": "https://yourapp.com/prisma/callback",
  "credentials": { "domain": "example.com" }
}

A business user of that profile approves access. The business needs Trustpilot’s API module on its account. One location per business unit. Replies can be replaced and deleted.

Yelp, Tripadvisor and Booking.com (beta)

"platform": "yelp" | "tripadvisor" | "booking" · listing URL · read only · Yelp, Tripadvisor, Booking.com

{ "platform": "tripadvisor", "listing_url": "https://www.tripadvisor.com/Restaurant_Review-g187514-d1234567-Reviews-Example_Cafe-Madrid.html" }

One connection is one listing. Prisma reads the public reviews of the listing through a data provider; connect only listings of businesses you own or manage. Each check collects up to 1,000 reviews, and results arrive a few minutes after the check starts. Read only: answer reviews on the platform, with the link in each review’s url.

Yotpo, REVIEWS.io and G2 (beta)

Credentials · read only · Yotpo, REVIEWS.io, G2

{ "platform": "reviews_io", "credentials": { "store": "example-store", "api_key": "your-private-api-key" } }

These platforms’ APIs can read reviews but not reply to them, so they are read only: each review’s url links to where you answer it. G2 answers 403 when the vendor’s G2 plan doesn’t include API access to reviews; Prisma returns that as 422 invalid_credentials at connection time.

Not supported

• Facebook: Meta removed the Page ratings API in Graph API v22.0.
• Amazon and Glassdoor: not supported.

The full overview, with setup notes, is on Integrations.

FAQ

Why can’t I reply to Yelp, Tripadvisor and Booking.com reviews through Prisma?

Those platforms have no API to reply to reviews for third parties. Prisma reads their reviews, and each review includes a url to answer it on the platform. A reply request returns 422 reply_not_supported. Prisma never logs into a customer’s account.

Is Facebook supported?

No. Meta removed the Page ratings API in Graph API v22.0. Amazon and Glassdoor are not supported either.

Do I need my own Google Cloud project?

No. Prisma uses its own Google Cloud project for the Business Profile API. The owner or a manager of the profile only approves access with OAuth.