What you can build

Pick the integration you need and follow its path from first call to full reference.

Most integrations combine a few of the paths below. Each path is marked with the token it needs:

  • Store token: for your own store, or a store you work on. Generate an access token from the store ID and API secret, then send it in the X-Yotpo-Token header.
  • App token: for app partners building one app for many merchants. You get a token per store when a merchant installs your app; see Authenticating with OAuth 2.0.
  • Public: storefront endpoints that need only the store ID, so you can call them from browser code.

Sync orders so review requests go out (store token)

Send each order and its fulfillment. Yotpo sends review requests only after a fulfillment with status: success and a fulfillment_date.

📘

Sending everything in one call

Send aggregated order info takes the order, customer, products and fulfillments in a single request, and creates products that don't exist yet.

Sync your product catalog (store token)

Products come first: orders and reviews refer to them by external_id.

Sync customers (store token)

Customers are created or updated by external_id or email, so the same call is safe to re-run in a sync job.

Install your app and make your first call (app token)

Every partner app starts here: the merchant installs your app, you exchange the install code for an access token, and you call the merchant's store.

Show reviews and star ratings on a storefront (public)

Render reviews in your own components: product pages, category pages, search results, mobile apps and recommendation widgets.

Show loyalty points on product pages (public)

Show "Earn X points" for each product and variant, based on the store's loyalty earning rules.

Make reviews readable by search engines and AI crawlers (public)

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

Bring reviews and Q&A into your platform (app token)

Use review content in emails and flows, show it next to customer records, or analyze it in a BI tool or CDP.

Read orders, products and customers (app token)

Read the merchant's store data, and update fulfillments so review requests go out at the right time.

Reward loyalty actions (app token)

Award points for actions that happen in your product, and show shoppers their balance and referral link.

React to events with webhooks (store or app token)

Get review, loyalty and app events pushed to your HTTPS endpoint instead of polling.

Migrate from the V1 API (store token)

Move V1 purchase and product calls to their V3 equivalents. V1 calls already accept the same access token in the X-Yotpo-Token header.


Did this page help you?