Yotpo API pricing, API key, reviews endpoints and rate limits
Yotpo publishes its API documentation for free and lets any store administrator generate an app key and secret, but it names API access on none of the plans it publishes. The prices Yotpo does print, on its Shopify listing, are Free up to 50 monthly orders, Starter at $15 a month and Pro at $119 a month, all marked as changing with order volume. Its own pricing page publishes no plan prices at all. So the honest answer to "what does the Yotpo API cost" is that it costs whatever your Yotpo subscription costs, and nobody outside Yotpo can tell you which tier unlocks it. Below are the two APIs, the exact token flow, the documented rate limits, and the cheaper route if all you want is reviews on your pages.
No token, no order volume tier
Sources
Layout
Brand color
Minimum rating
No reviews match those filters
Turn a source back on or lower the minimum rating.
·
reviews shown
from Google · G2 · direct
Drops next to any CTA: signup, pricing, checkout.
Paste this once, anywhere in your HTML. The widget inherits your settings from the studio and stays in sync when you change them.
Create your account to activate your embed code.
Automated request email
From: Your Company <[email protected]>
Subject: Quick favor? It takes 40 seconds
Hi Jordan,
You've been with us for 3 months, thanks for that. Would you share how it's going? One click below, 40 seconds, done.
Sent automatically 90 days after signup · timed to the customer's timezone
See it land in your own inbox
We'll send you this exact sequence the way your customers would receive it.
Most people who search for the Yotpo API want reviews rendering on their own pages. That is a script tag, not an integration project. Our widget covers Google, G2, Trustpilot and direct reviews on flat pricing.
The question behind most Yotpo API searches
How much does the Yotpo API cost?
There is no per call rate, no developer plan and no add on line item. Yotpo sells subscriptions and the API sits somewhere inside one, which is why the price you are looking for is not published anywhere.
| Plan | Published price | Volume condition | Does the listing name API access? |
|---|---|---|---|
| Free | $0 | Up to 50 monthly orders | No |
| Starter | $15 a month, or $144 a year | "Pricing changes based on order volume" | No |
| Pro | $119 a month, or $1,068 a year | "Pricing changes based on order volume" | No |
| Anything above Pro | Not published | Quote based | Not published |
The prices move with your orders
Both paid tiers carry the same footnote: pricing changes based on order volume. $15 and $119 are floors for a small store, not the number a growing brand pays. Budget from a quote, not from the listing.
The main pricing page shows nothing
Checked in September 2026, yotpo.com/pricing routes you to a sales form rather than a plan table with prices. The Shopify app listing is currently the only place Yotpo prints a number.
"Premium includes the API" is secondhand
Several pricing round ups state that a Premium tier carries API access. None of them cites a Yotpo page, and Yotpo publishes nothing that says it. Treat it as a rumor and get the entitlement in your order form.
Pick the right one before you write code
Yotpo ships two separate APIs, and people usually start on the wrong one
The names do not help. Core sounds foundational and UGC sounds niche, but if your job is getting reviews out of Yotpo, UGC is the one you want.
| UGC API | Core API v3 | |
|---|---|---|
| What it does | Reads and writes reviews, scores, sentiment, questions and visual content | Syncs your product catalog, customers, orders and fulfillments into Yotpo |
| Direction | Mostly data out | Data in |
| Reference | apidocs.yotpo.com | core-api.yotpo.com |
| Base URL | https://api.yotpo.com |
https://api.yotpo.com/core/v3/stores/{store_id} |
| Token exchange | POST /oauth/token with client_id, client_secret, grant_type |
POST .../access_tokens with your secret in the body |
| Auth header | X-Yotpo-Token |
X-Yotpo-Token |
| Versions in play | v1 supported, v3 rolling out for storefront reviews | v3 |
Yotpo is rolling out version 3 of the UGC API beginning with storefront reviews, and recommends it if your job is displaying product or store reviews. Its own reference is explicit that version 1 is not being switched off, so an existing v1 integration is not on a deadline. Everything outside storefront reviews still lives in the v1 reference.
The second most searched Yotpo API question
How to get a Yotpo API key and secret
The app key is visible to anyone with admin access to the store. The secret takes an email verification step, and staff level users cannot see it at all.
Open Account Settings
In the Yotpo admin, click the profile icon at the top right of the screen and choose Account Settings, then General Settings.
Copy the app key
Your app key sits at the bottom of the General Settings section. This is the same value the docs call your store ID and the value you pass as client_id.
Generate the secret
Click Get secret key. Yotpo emails a verification code to the address on the account. Paste it, submit, and the secret is revealed on the next screen.
Exchange for a token
POST the app key as client_id and the secret as client_secret to /oauth/token with grant_type set to client_credentials, then send the bearer token in X-Yotpo-Token.
Two things that catch teams out
The API secret is visible only to Yotpo account administrators. If your developer holds staff permissions, they can see the app key and not the secret, so the credential handoff has to come from whoever owns the account. And the token is meant to be stored and reused rather than requested on every call, which matters because the rate limit below is counted per store, not per process.
What the documentation actually commits to
Yotpo API rate limits, in numbers
Yotpo documents a global ceiling and separate per endpoint ceilings, and the global one is far tighter than people expect for a bulk export.
| Limit | Value | Scope | What happens at the ceiling |
|---|---|---|---|
| Global API rate | 5 requests per second | Per store | 429 Too Many Requests |
| Retrieve all reviews | 5,000 requests per minute | Per app key | 429 Too Many Requests |
| Create review | 5,000 requests per minute | Per app key | 429 Too Many Requests |
| Recommended backoff | 1 second | Per retry | Read RateLimit-Remaining and RateLimit-Reset |
The two numbers look contradictory until you notice the scopes. The per endpoint ceiling of 5,000 a minute is generous, but the 5 per second store ceiling is the one that binds, because it applies across every process talking to Yotpo on your behalf. Five per second works out to 300 a minute, so a nightly job that pulls every review and a middleware that syncs orders are competing for the same budget. Read the RateLimit-Remaining and RateLimit-Reset headers on every response rather than guessing, and hold to the documented one second backoff after a 429.
The endpoint everyone lands on
What the Yotpo reviews endpoint returns
Retrieve all reviews is the workhorse. It takes your store ID in the path, your token in a header, and it supports incremental pulls, which is what keeps you under the rate limit.
Fields in a review object
Each review carries an ID, title, content, score, sentiment, reviewer details, created and updated timestamps, and a flag showing whether the review was incentivized. That last field matters more than it looks: if you republish reviews elsewhere, incentivized content usually has to be labeled, and this is where you find out which ones are.
Parameters worth knowing
Page with count and page. Pull only what changed with since_id, since_date or since_updated_at. Set deleted to true to include unpublished reviews, and filter a single record with id or a customer with user_reference.
Build incremental from day one
A full re-pull of a large catalog every night is exactly what trips the 5 per second store limit. Store the highest updated_at you have seen and pass it as since_updated_at on the next run. The job goes from thousands of calls to a handful, and it stops competing with your order sync.
Reviews are not the only content
The same UGC reference covers questions and answers, visual content and the privacy endpoints. If you are building a customer data deletion flow for a privacy request, that lives here too, and it is worth mapping before you ship anything customer facing.
Before you open a ticket with your account manager
Do you actually need the Yotpo API?
Three genuinely different jobs bring people to this page, and only one of them needs an API at all.
You want reviews on your site
Then no. Yotpo ships on site widgets on every plan including Free, and a third party widget renders reviews with a script tag. Writing an integration to fetch reviews and re-render them yourself is weeks of work to replace a paste.
You want review data in a warehouse
Then yes, this is the real case. Incremental pulls into BigQuery, Snowflake or a Postgres table, joined to orders, are what the UGC API is for. Budget for the 5 per second store ceiling and build the sync as a queue, not a loop.
You run a headless storefront
Then yes, and start on UGC v3 rather than v1. Yotpo publishes a headless integration guide for exactly this, and v3 is the version it is pushing for storefront reviews. Cache aggressively so product pages are not calling Yotpo per render.
Where ReviewJet fits, honestly
We are not a Yotpo replacement for product reviews
Yotpo is built around product level reviews on an ecommerce catalog. That is a different job from ours, and it is worth being straight about which one you have.
If you sell physical products and need a star rating under every SKU, syndicated photo reviews and Google Shopping feeds, Yotpo is a reasonable place to be and this page is here to help you use it, not talk you out of it.
Where teams overpay is the other job: the reviews that decide whether someone trusts the business. Those live on Google, G2 and Trustpilot, not on your product pages, and Yotpo is not where you collect or display them. ReviewJet does that side. We send the review requests, monitor what comes back across Google, G2, Trustpilot and direct reviews, and render all of it in one widget with a script tag. Flat pricing from $24 a month billed yearly, with no order volume multiplier and no negotiation about which tier gets an API.
Two different review problems
Product reviews
Star ratings per SKU, photo and video UGC, rich snippets on product pages, retailer syndication. Yotpo, Bazaarvoice, Okendo and Judge.me compete here.
Business reviews
Your Google Business Profile rating, your G2 or Trustpilot profile, the reviews a buyer reads before they trust you at all. ReviewJet, Birdeye and Podium compete here.
Most brands have both
Which is why the two categories rarely replace each other. Running a product review app and a business review platform side by side is normal, and cheaper than forcing one to do both.
Questions people search before they build
Yotpo API questions, answered
Keep reading
Related review API and pricing pages
Yotpo pricing
Every published Yotpo number, what the order volume footnote actually does to the bill, and where the cheaper alternatives sit.
G2 API pricing
The same question one category over: G2 marks Reviews API Access on the Enterprise tier alone and publishes no price for it.
Trustpilot API
The add on that sits on a $319 a month floor, the public and private endpoint split, and the record ceiling.
Google Reviews API pricing
The five review cap on Places, the per thousand call rate, and the Business Profile approval process.
Review API pricing compared
Google, Trustpilot, Yelp, G2 and TripAdvisor side by side: what each one charges and what each one actually returns.
Yotpo alternatives for Shopify
What Okendo, Loox and Judge.me charge against Yotpo, and which one fits a store at your order volume.
Business reviews on your site without an integration project
Google, G2, Trustpilot and direct reviews in one widget, with request sequences that grow the number you have. Flat pricing from $24 a month, no order volume multiplier.
From $24/mo, billed yearly. No per-review fees.