Reference · built on requestConnectorMarketing, reviews & analytics

Judge.me

Product and store reviews, reviewers, ratings, and review webhooks from a Judge.me shop through the Judge.me REST API.

Request accessPricing ↗

About

Judge.me is a product review app for e-commerce stores. A shop's reviews, reviewers, ratings, replies and widget settings sit behind the Judge.me REST API at api.judge.me, keyed by the shop's domain. The same API registers webhooks that fire when a review is created or updated, and serves rendered widget HTML for storefronts.

Through Fibric, an operator listens for review/created and review/updated webhooks, joins each review to the order and customer behind it, and proposes a public reply, a private email reply, or a publish-or-hide decision for a person to approve. Each approved action is applied once and leaves a receipt.

This is a reference listing. It documents what Fibric would read from Judge.me and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Product and store reviews with rating, body, reviewer and product through GET /api/v1/reviews, filtered by product_id, reviewer_id or rating
  • A single review through GET /api/v1/reviews/{id} and review totals through GET /api/v1/reviews/count
  • Reviewer name and email through GET /api/v1/reviewers/{id}, found by Judge.me id, external_id or email
  • review/created, review/created_fail and review/updated webhooks registered through POST /api/v1/webhooks
  • Shop-level review count and average rating through the all_reviews_count and all_reviews_rating widget endpoints
  • Shop information and settings through GET /api/v1/shops/info and GET /api/v1/settings

Proposed actions

  • Target capability: propose a public reply to a review through POST /api/v1/replies
  • Target capability: propose a private email reply to a reviewer through POST /api/v1/private_replies
  • Target capability: propose publishing or hiding a review by setting curated to ok or spam through PUT /api/v1/reviews
  • Target capability: propose a manual review request for an order through the send_manual_review_request endpoint

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Reply to a low rating with the order open

    On review/created with a one- or two-star rating, pull the order and prior support thread, and propose a public reply for someone to edit and approve.

    With Review Response

  • Reach a detractor privately first

    Propose a private email reply through POST /api/v1/private_replies so a person can resolve the problem before deciding whether to answer in public.

    With Detractor Callback

  • Hold suspect reviews for a human

    When a review's reviewer matches no order, propose hiding it with curated set to spam and leave the decision to a person.

    With Noise Filter

  • Track which products draw complaints

    Group reviews by product and rating across the week and surface the recurring themes with example quotes.

    With Feedback Themes

Requirements

  • A Judge.me shop and admin access to Settings > Integrations to view API tokens
  • The shop domain in myshopify.com format, passed as shop_domain on API-key calls
  • For an OAuth app, only the scopes the job needs, such as read_reviews, read_reviewers, write_replies and write_private_replies
  • An HTTPS webhook endpoint with a valid SSL certificate to receive review events
Authentication
A private API token from Settings > Integrations in the Judge.me admin, sent in the X-Api-Token header with the shop_domain parameter, or an OAuth 2.0 access token from a Judge.me app sent as Authorization: Bearer.

Limits

  • Review endpoints return raw data that can include unpublished reviews and unsanitized text; storefront display goes through the widget endpoints
  • Review lists page at up to 100 reviews per request
  • Webhook requests are checked with the JUDGEME-HMAC-SHA256 header; the secret differs between OAuth apps and private tokens
  • Judge.me's Cache Server is on the Awesome plan only; the Widget API is on the Free plan

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Judge.me ↗

Questions and answers

Does Judge.me send webhooks?
Yes. POST /api/v1/webhooks registers a key and a URL. Documented keys include review/created, review/created_fail, review/updated and widget/settings/updated. Each request carries a JUDGEME-HMAC-SHA256 header. Check it with the OAuth app's secret, or with the private API token when the webhook was created with one.
Which credentials does the connector use?
A private API token with the shop_domain parameter, or an OAuth 2.0 access token. Public tokens are for widget GET calls in browser code. Judge.me recommends OAuth for integrations, requesting only the permissions the job needs, such as read_reviews or write_replies.
Can the connector publish or hide a review?
Yes, as a proposal. PUT /api/v1/reviews accepts curated set to ok to publish or spam to hide. A person approves each change. Judge.me notes that review endpoints return raw content, so the connector never renders review text to a storefront.
Ask about Judge.me

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Judge.me through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy