Reference · built on requestConnectorMarketing, reviews & analytics

Yotpo

Reviews, ratings, Q&A, and review-request events from Yotpo, with Core API orders that start the request.

About

Yotpo is a reviews and user-generated content platform for online stores. A store holds product and site reviews with scores and sentiment, questions and answers, customer photos, and the orders that drive review requests after fulfillment or delivery. The UGC API at api.yotpo.com serves reads and writes; api-cdn.yotpo.com serves search and storefront reads; the Core API v3 holds products, customers, orders, and webhooks.

Through Fibric, an operator reads new and changed reviews, joins them with the order and any support case, and proposes a reply to a question, an order post that starts the review request, or a hold in another system for your approval. Every approved write happens once and is logged with its reason.

This is a reference listing. It documents what Fibric would read from Yotpo 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

  • Reviews through GET /v1/apps/{store_id}/reviews, with score, title, content, sentiment, sku, reviewer_type, and votes, up to 100 per page
  • Incremental pulls with since_date, since_id, or since_updated_at, and unpublished reviews when deleted is true
  • Review search through POST /v1/reviews/{store_id}/filter.json on api-cdn.yotpo.com, filtered by score, topic, product, reviewer type, or free text
  • Bottom line totals and average score for the whole store or one product
  • Questions and answers on products
  • Core API webhooks for review_create, review_updated, review_request.eligible.on_fulfillment, and review_request.eligible.on_delivery
  • Orders, order fulfillments, products, and customers synced to the store through the Core API v3

Proposed actions

  • Target capability: propose an answer to a customer question through Create Answer for Question
  • Target capability: propose an order record through POST /core/v3/stores/{store_id}/orders so Yotpo sends the review request after fulfillment
  • Target capability: propose a change to a review's incentivized flag through Update Incentivized Reviews by Review ID

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

What you can build

  • Answer a low-star review through the right channel

    A review_create webhook arrives with a score of 1 or 2. The operator matches the reviewer to the order and support history and proposes a reply draft, plus a follow-up ticket for your team.

    With Review Response, Review Reply

  • Find the theme behind a rating drop

    The operator pulls recent reviews by sku and sentiment, groups the complaints, and proposes a summary with the products and dates involved.

    With Feedback Themes, Sentiment Spike

  • Send the review request after delivery, not shipment

    The operator posts orders and fulfillments as your store reports them, so review_request.eligible.on_delivery fires when the parcel arrives. Each order is posted once; a repeat returns 409.

    With Survey Timing

  • Hold a product with a quality complaint

    When several reviews on one sku report the same defect, the operator proposes a hold in your inventory system and attaches the review ids as evidence.

    With Quality Hold

Requirements

  • A Yotpo Reviews account, its Store ID (formerly App Key), and the API secret, which only the account administrator can see
  • For review requests, orders posted to the Core API with external_id, order_date within six months, customer, and line_items
  • For webhooks, an HTTPS callback URL under 2,048 characters, registered as a target, with a filter and a subscription
Authentication
An access token from POST /oauth/token with your Store ID as client_id, your API secret as client_secret, and grant_type client_credentials, sent on each request in the X-Yotpo-Token header.

Limits

  • Retrieve all reviews allows 5,000 requests per minute per app key; the Core API allows 5 requests per second per store
  • Search results on api-cdn.yotpo.com lag by about 3 hours
  • Yotpo cannot send automatic review requests for orders older than six months
  • Create Review is asynchronous and emails a verification link to each customer named, so it does not suit importing moderated reviews

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 Yotpo ↗

Questions and answers

How does the connector authenticate?
It exchanges your Store ID and API secret for an access token at POST /oauth/token with grant_type client_credentials, then sends the token in the X-Yotpo-Token header. Tokens can expire; a 401 means generate a new one. Only the account administrator can see the secret.
Does Yotpo push review events?
Yes, through Core API webhooks. You create a target with your callback URL, a filter with the topics, and a subscription that links them. Topics include review_create, review_updated, review_request.eligible.on_fulfillment, and review_request.eligible.on_delivery. Each delivery carries a WebhookMessageIdPerTarget header and is retried at least 10 times with exponential backoff.
How far back can reviews be pulled?
Retrieve all reviews accepts since_date, since_id, and since_updated_at, with up to 100 reviews per page and deleted set to true to include unpublished ones. The endpoint allows 5,000 requests per minute per app key. Search on api-cdn.yotpo.com is faster to query but lags by about 3 hours.
Ask about Yotpo

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.