What you can build

Pick what you want to build and follow the path. Each one starts with a short recipe and links to the guides and reference pages you need next.

Most integrations fall into one of the paths below. Storefront paths use the public V3 storefront endpoints and need no token. Merchant paths run on your server and need an access token (see Authenticate and make your first call).

Show reviews and star ratings on a product page

Fetch a product's star rating and a page of reviews, and render them in your own components. This is the usual starting point for headless storefronts.

Show star ratings on category pages

Show a rating on every product card without calling the API once per product.

Let shoppers search and filter reviews

Add free-text search, star filters, photo filters, and topic chips to your reviews section.

Show an AI review summary and featured reviews

Display Yotpo's AI-generated summary and topics above your reviews, or a carousel of top reviews on a product page or home page.

Collect reviews from your own form

Submit reviews and photos from a form you build, and let shoppers vote reviews helpful. Send these calls from your server.

Make reviews readable by search engines and AI crawlers

Put ratings and reviews in your page source so search engines and AI assistants can read them.

Export reviews to your own systems

Pull all of your store's reviews into a data warehouse, CRM, or support tool. Add deleted=true to include deleted reviews. Runs on your server with an access token.

Handle privacy requests

Check whether Yotpo holds a shopper's data, export it, or delete it in response to a privacy request.

More you can build

  • Questions and answers: show and collect product Q&A. See About Q&A.
  • Visual UGC galleries: Instagram and imported media, albums, and product galleries. See About Visual UGC.
  • Review insights: topics and sentiment across your reviews. See About Insights API.
  • Not sure where to start? Read Guidelines & Conventions for base URLs, pagination, rate limits, and errors.
  • Before you go live: read Errors for how to handle each status code, and Testing your integration for which calls send emails or change data permanently.

What’s Next

Guidelines and conventions for base URLs, pagination, and errors

Did this page help you?