E-Commerce · Beta

Judge.me
API integration

Ship E-Commerce features without building the integration. Full Judge.me API access via Proxy and 30+ MCP-ready tools for AI agents — extend models and mappings to fit your product.

Built for specific customer use cases. Issues are resolved quickly.

Talk to us

Use Cases

Why integrate with Judge.me

Common scenarios for SaaS companies building Judge.me integrations for their customers.

Embed review management inside e-commerce helpdesks

Support platforms can let agents monitor Judge.me reviews and respond publicly or privately without leaving the helpdesk UI, turning negative feedback into resolved tickets.

Trigger loyalty rewards from verified reviews

Loyalty and rewards SaaS can subscribe to review events via webhooks and automatically issue points when shoppers submit qualifying reviews, closing the loop between UGC and retention.

Enrich e-commerce analytics with sentiment data

CDPs and analytics tools can pull review content, ratings, and product-level aggregates to correlate customer sentiment with sales, returns, and merchandising decisions.

Power headless storefronts and mobile apps with review UI

Page builders and mobile app platforms can fetch Judge.me widget HTML and aggregate ratings to render native review experiences without rebuilding frontend components.

Seed and sync reviews for dropshipping and migration tools

Product sourcing and store migration apps can programmatically create reviews in a merchant's Judge.me account to guarantee day-one social proof on new stores.

What You Can Build

Ship these features with Truto + Judge.me

Concrete product features your team can ship faster by leveraging Truto’s Judge.me integration instead of building from scratch.

Public and private reply automation

Let users respond to Judge.me reviews from your app by posting public replies on the storefront or sending private email responses to the reviewer.

Review moderation workflows

Build queues where users can approve, hide, or edit reviews at scale using update operations on individual review records.

Real-time review event subscriptions

Register Judge.me webhooks on behalf of your users to trigger downstream automations the moment a review is submitted, updated, or published.

Product and shop rating widgets in your UI

Fetch preview badges, star ratings, verified badges, and featured carousels to render Judge.me social proof natively inside your product's dashboards or storefront blocks.

Reviewer data request handling for GDPR compliance

Programmatically create reviewer data requests and update reviewer profiles so your users can honor privacy obligations from within your platform.

Bulk shop and webhook management

Onboard multi-store merchants at scale with bulk create, update, and delete operations for shops and webhook subscriptions.

SuperAI

Judge.me AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

list_all_judge_me_widgets_product_reviews

Review Widget is usually placed at the bottom of each product page, displaying all reviews of a product. You can use product handle, external ID, or Judge.me internal ID to specify the product. The upstream spec does not document a response body for this endpoint.

list_all_judge_me_widgets_preview_badges

Preview Badge is usually placed below product titles on product pages or inside product thumbnails on collection pages. This widget display the average star rating and review count of each product. You can use product handle, external ID, or Judge.me internal ID to specify the product. The upstream spec does not document a response body for this endpoint.

list_all_judge_me_widgets_featured_carousels

Reviews Carousel is usually placed on the homepage to showcase specific reviews featured by the store in Judge.me. The upstream spec declares an application/json response but does not document its fields.

list_all_judge_me_widgets_reviews_tabs

Floating Reviews Tab display all product and store reviews via a floating button on any pages in Judge.me. The upstream spec does not document a response body for this endpoint.

list_all_judge_me_widgets_all_reviews_pages

All Reviews Page is a dedicated page to showcase all product and store reviews all in one place in Judge.me. The upstream spec declares an application/json response but does not document its fields.

list_all_judge_me_widgets_verified_badges

Verified Reviews Count Badge displays the number of verified published reviews. Stores need at least 20 verified reviews to use this widget in Judge.me. The upstream spec declares an application/json response but does not document its fields.

list_all_judge_me_widgets_all_reviews_counts

Return a single total number of product and store reviews in Judge.me. The upstream spec declares an application/json response but does not document its fields.

list_all_judge_me_widgets_all_reviews_ratings

Return a single number of average rating of product reviews and store reviews in Judge.me. The upstream spec declares an application/json response but does not document its fields.

list_all_judge_me_widgets_shop_reviews_counts

Return a single total number of store reviews in Judge.me. The upstream spec declares an application/json response but does not document its fields.

list_all_judge_me_widgets_shop_reviews_ratings

Return a single number of average rating of store reviews in Judge.me. The upstream spec declares an application/json response but does not document its fields.

list_all_judge_me_widgets_settings

Return widget settings of the shop in HTML format, containing a script tag and a style tag. This carries the widget customization values in Judge.me such as text and colour, which let you render the widget correctly. The upstream spec declares an application/json response but does not document its fields.

list_all_judge_me_widgets_html_miracles

Return special HTML that helps show essential parts of widgets before the JS and CSS files are loaded in Judge.me. The upstream spec declares an application/json response but does not document its fields.

list_all_judge_me_widgets_checkout_comments_widgets

Return Checkout Comments widget for a product (for Checkout Comments app only). You can use product handle, external ID, or Judge.me internal ID to specify the product. The upstream spec does not document a response body for this endpoint.

list_all_judge_me_reviews

Get info of reviews of a product. If product_id is not provided, return all product and store reviews of that store in Judge.me. Returns: id, title, body, rating, pinned, product_external_id, product_title, product_handle, reviewer, source, curated, hidden, and more.

create_a_judge_me_review

Create a web review in background, similar to submitting a review via the public form on product pages (no authorization required). This endpoint doesn't create any review if the store disables web reviews in Judge.me. The upstream spec does not document a response body for this endpoint. Required: shop_domain, platform, email, name, rating, body.

update_a_judge_me_review_by_id

Publish or hide a Judge.me review via your app interface. For authenticity reason, we don’t support editing reviews via API. Returns: message. Required: id.

get_single_judge_me_review_by_id

Get info of a specific review in Judge.me. Returns: id, title, body, rating, pinned, product_external_id, product_title, product_handle, reviewer, source, curated, hidden, and more. Required: id.

list_all_judge_me_reviews_counts

Get count of reviews for a specific product or reviewer. If product_id is not provided, return the count of all product and store reviews of that store in Judge.me. The upstream spec does not document a response body for this endpoint.

get_single_judge_me_reviewer_by_id

Get information of the reviewers such as name and email. This is useful when you are building automated flow for users to follow up with reviewers in Judge.me. Returns: reviewer. Required: id.

update_a_judge_me_reviewer_by_id

Create or update a reviewer via your app interface in Judge.me. Returns: reviewer. Required: id.

create_a_judge_me_reviewers_data_request

Submit a GDPR-style data request for a reviewer in Judge.me, asking for the data held about a customer and the orders it relates to. Required: customer (with email).

list_all_judge_me_webhooks

List all webhooks registered in Judge.me for the shop. Returns: id, failure_count, key, url, created_at, updated_at.

create_a_judge_me_webhook

Create a webhook in Judge.me: when the event associated with the webhook's key happens, Judge.me sends a POST request to the webhook's url. Returns: shop_id, shop_domain, webhook.

get_single_judge_me_webhook_by_id

Get a single webhook in Judge.me by id. Returns: shop_id, shop_domain, webhook. Required: id.

update_a_judge_me_webhook_by_id

Update a webhook in Judge.me by id. Returns: shop_id, shop_domain, webhook. Required: id.

judge_me_webhooks_bulk_delete

Delete a Judge.me webhook identified by its event key and url. Returns an empty 204 response on success.

create_a_judge_me_webhooks_bulk_create

Bulk Create in Judge.me. The upstream spec does not document a response body for this endpoint.

list_all_judge_me_shops_info

Get the current Judge.me shop information, including plan, domain and contact details. Returns: id, awesome, country, created_at, currency, custom_domain, dmarc_ok, domain, email, name, onboarding_progress, owner, and more.

create_a_judge_me_shop

Create a checkout comment in Judge.me. Requires a JSON body; accepts content, external_product_id, create_from (checkout_page or email), and a customer object (first_name, last_name, email, external_id). Only available with the Checkout Comments app. Returns a 200 confirmation; the upstream docs do not document a response body shape.

judge_me_shops_bulk_update

Update the current Judge.me shop's store information. Requires a JSON body with the fields to change — domain, custom_domain, email, owner, phone, name, country, timezone, plan — all optional. Returns a generic success confirmation (success).

judge_me_shops_bulk_delete

Uninstall a store from Judge.me, removing the shop's Judge.me integration. Takes no parameters. Returns an empty 204 response on success.

list_all_judge_me_settings

Get multiple settings values of the store in Judge.me, which can serve as conditions for your app integrations. Returns: settings.

create_a_judge_me_reply

Create a public reply to a Judge.me review, displayed on the public review widget. Returns an empty success response on 200; if the reply cannot be created, a 422 with an error message is returned. Requires a JSON request body following Judge.me's RequestCreateReply schema. Required: review_id, reply.

create_a_judge_me_private_reply

Create a private email reply to a Judge.me review privately via your app interface. The upstream spec does not document a response body for this endpoint. Required: review_id, private_reply.

Why Truto

Why use Truto’s MCP server for Judge.me

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 800+ integrations.

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

How It Works

From zero to integrated

Go live with Judge.me in under an hour. No boilerplate, no maintenance burden.

Link your customer’s Judge.me account

Use Truto’s frontend SDK to connect your customer’s Judge.me account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

Call our API, we call Judge.me

Truto’s Proxy API is a 1-to-1 mapping of the Judge.me API. You call us, we call Judge.me, and pass the response back in the same cycle.

Unified response format

Every response follows a single format across all integrations. We translate Judge.me’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about Judge.me on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

How does authentication work for Judge.me through Truto?

Truto handles the Judge.me credential exchange and token storage for you. Your end users connect their Judge.me account once, and Truto manages the auth handshake so your app can call the API without storing shop tokens directly.

Can I subscribe to review events instead of polling?

Yes. Use the webhook tools to register, list, update, and bulk-manage Judge.me webhook subscriptions so your app receives events (like new reviews) in real time rather than polling the reviews list.

Can I reply to reviews programmatically?

Yes. Truto exposes both public replies (posted on the product review page) and private replies (delivered to the reviewer via email), so support and marketing tools can respond directly through the API.

Can I create reviews on behalf of a merchant?

Yes. The create review tool lets migration, dropshipping, and seeding tools push review records into a merchant's Judge.me account, which is useful for populating new stores or importing from other sources.

How do I get aggregate ratings without fetching every review?

Judge.me exposes lightweight widget endpoints for all-reviews counts, all-reviews ratings, shop review counts, and shop review ratings, so you can display totals and averages without paginating through the full review dataset.

Does the integration support multi-shop merchants?

Yes. Shop-level tools include list, create, bulk update, and bulk delete operations, which makes it straightforward to onboard and manage merchants running multiple Judge.me shops.

Can I render Judge.me UI inside a headless storefront?

Yes. Widget tools for product reviews, preview badges, featured carousels, reviews tabs, all-reviews pages, verified badges, and HTML miracles return renderable widget content that headless and mobile builders can inject into custom frontends.

From the Blog

Judge.me integration guides

Deep dives, architecture guides, and practical tutorials for building Judge.me integrations.

Judge.me

Get Judge.me integrated into your app

Our team understands what it takes to make a Judge.me integration successful. A short, crisp 30 minute call with folks who understand the problem.