Okendo API: access cost, Merchant REST API key and Okendo reviews API documentation
Okendo has two APIs and they are gated completely differently. The Storefront REST API is public: it reads your published reviews with no credential at all, just your Okendo User ID in the URL. The Merchant REST API, the one that lists pending reviews, updates them, posts replies and touches customers and loyalty, is not. Okendo's own help center says you need the Advanced plan or above, or purchased Merchant REST API access on a lower plan, and Okendo prints no price for either route. Below is what Okendo actually publishes, read at source in September 2026.
Store reviews, no API key
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.
Your Google, G2, Trustpilot and direct reviews on any page in one script tag. We are not a Shopify product review app, so if you need star ratings on every SKU, Okendo is the right category and this page prices its API honestly.
The question behind most Okendo API searches
How much does the Okendo API cost?
Okendo publishes four plan prices and none of them includes the Merchant REST API. The plan that does include it has no published price, and neither does the add-on. Here is exactly what is printed and what is withheld, read on 10 September 2026.
| What buyers ask | Published by Okendo | What it actually says |
|---|---|---|
| Entry plan prices | Yes, on the Shopify listing | Free up to 50 orders a month, Essential $19 up to 200, Growth $119 up to 1,500, Power $299 up to 3,500 |
| Which plan includes the Merchant REST API | Yes, in the help center | "Advanced plan or above or have purchased Merchant REST API access (for plans below Advanced)" |
| Price of the Advanced plan | No | Advanced is not one of the four plans on the Shopify listing, and Okendo's pricing page asks you to pick an order band instead of printing a figure |
| Price of the API add-on | No | "available as a paid add-on for Power plan subscribers", with no amount |
| Storefront REST API | Yes | Public and unauthenticated, scoped by your Okendo User ID, reading published content only |
| API rate limits | No number | No requests per second or per day ceiling in the public documentation |
| Enterprise tier | Name only | Okendo Platform Scale: "Custom pricing", "No usage caps", a fixed annual price for unlimited orders |
You will find a figure for Okendo Advanced on review blogs, usually $499 a month. Treat it as secondhand. It does not appear on any Okendo page we could read, and the blogs quoting it disagree with each other on the order volume it covers, one citing 2,500 orders a month and another 10,000. Numbers that cannot agree on what they buy are not a budget. If the API is the reason you are upgrading, the honest move is to ask Okendo for two quotes in writing, Advanced and Power plus the API add-on, at your forecast order volume, and compare those.
Okendo API documentation, in one table
Storefront REST API vs Merchant REST API
Most confusion about the Okendo API comes from treating it as one thing. It is two, with different hosts, different authentication and different plan gates. Pick the wrong one and you either leak a secret or wait on a sales call you did not need.
| Storefront REST API | Merchant REST API | |
|---|---|---|
| Base URL | api.okendo.io/v1 | api.okendo.io/enterprise |
| Authentication | None. Your Okendo User ID goes in the path | HTTP Basic: User ID as the username, a 32 character API key as the password |
| Version header | Not required | okendo-api-version on every request, a dated value such as 2025-02-01 |
| What it does | Reads published reviews, rating aggregates, review media and questions | Lists, retrieves, updates and replies to reviews; customers, loyalty, review groups, translation blocklists and webhook subscriptions |
| Where it may run | Browser, storefront or any public client | Server side only. Okendo warns client side use "will put your data at risk" |
| Plan gate | No key to request | Advanced and above, or purchased access below Advanced |
The practical rule is short. If all you need is to show approved reviews somewhere Okendo's widgets do not reach, such as a headless storefront, a native app or a landing page outside Shopify, the Storefront REST API does it today on any plan and you never touch a key. If you need to read pending reviews, change their status, reply from another tool, or move every review into a warehouse including the ones that were never published, that is Merchant REST API territory, and the plan conversation comes first.
Where integrations actually stall
How to get an Okendo API key
Generating the key takes a minute. Being allowed to use it is the part that takes a week, because it depends on a plan decision somebody else signs.
1
Confirm the plan covers it
Check whether the store is on Advanced or above, or has bought Merchant REST API access. On Free, Essential or Growth the path is an upgrade. On Power it is the paid add-on. Ask before you build, because nothing in the Shopify listing will tell you and a working key on the wrong plan is not something to rely on.
2
Copy the User ID
In the Okendo app open Settings, then Integrations, and select the Okendo section. Copy your User ID. This one value does double duty: it is the path segment for every Storefront REST API call and the username half of Merchant REST API authentication.
3
Generate the Merchant REST API Key
On the same screen, if a key has not been created before, select Generate and copy the value. Okendo describes the password as a unique, 32 character string. Put it straight into your secrets manager, not a shared doc, since it grants write access to reviews and loyalty balances.
4
Send both headers, from a server
Base64 encode User ID, a colon and the key, and send it as Authorization: Basic. Add the okendo-api-version header with a dated value and pin it in code. Keep all of this on a server. A Merchant key shipped in front end JavaScript is readable by every visitor.
Compared with the rest of the category this is a friendly flow. There is no second person approving the key, which is how Bazaarvoice works, and no emailed verification code, which is how Yotpo guards its secret. The friction at Okendo is purely commercial: the key is easy to generate and the right to use it is sold by plan.
Okendo reviews API in practice
How an Okendo reviews request is built
Both APIs return reviews as a collection with a link to the next page. The difference is what you are allowed to see and change.
Storefront: published reviews, no key
Okendo's own help center uses this exact format for pulling reviews into Klaviyo emails:
GET https://api.okendo.io/v1/stores/{okendo_user_id}/reviews?limit=5&orderBy=rating%20desc
- limit takes 1 to 100 and defaults to 25.
- orderBy takes date desc, date asc, rating desc, rating asc, helpful desc, helpful asc or has_media desc. The default is date desc.
- Per product and store wide review endpoints both exist, so you can render a single SKU or a whole store feed.
One commercial catch: the help center lists dynamic review blocks in Klaviyo, the feature built on this endpoint, as available on Power plans and above. The endpoint is public, but Okendo packages the ready made use of it as a Power feature.
Merchant: the whole queue, with write access
The Merchant REST API reference names four review operations: List reviews, Retrieve a review, Update a review and Reply to a review. The list call filters by status, approved, pending or rejected, which is the piece the Storefront API can never give you, because it only sees what is already published.
Paging is cursor based. Each response carries a link to the following page and you follow it until none comes back. With a ceiling of 100 per call, a store holding 40,000 reviews is at least 400 requests for a full backfill, which is fine once and wasteful every night.
The better pattern is one backfill, then webhook subscriptions. The reference includes create, list, update and delete operations for webhook subscriptions plus a call to rotate a subscription's secret, so new and changed reviews can be pushed to you instead of being polled for.
Okendo API limits
The limits and gotchas worth knowing before you build
None of these are hidden, but they are spread across a developer site, a help center and a Shopify listing, so most teams find them one at a time.
| Limit or gotcha | What Okendo documents | What to do about it |
|---|---|---|
| Rate limit | No published number | Sync incrementally, back off on a 429, and ask your Okendo contact for the real ceiling before a large backfill |
| Results per request | limit 1 to 100, default 25 | Always pass limit=100 on backfills; the default quadruples your request count |
| Versioning | A dated okendo-api-version header on every Merchant call | Pin the date in config and upgrade on purpose, never to whatever is newest |
| Retries | No idempotency key contract | Do not blindly retry Update or Reply calls, or a timeout can post the same reply twice |
| Public reads | Storefront API needs only the User ID | Assume anyone can read your published reviews and aggregates; nothing private is exposed, but plan for it |
| Retail syndication | Bazaarvoice syndication is Advanced and above, with your own Bazaarvoice contract | Fill the Shopify barcode field with UPC, GTIN or EAN first; that is how retailer listings are matched |
The syndication row matters more than it looks if API access is only half the reason you are upgrading. Okendo's help center describes sending reviews to "2,300+ retailer sites worldwide through the Bazaarvoice network", with the product catalog updated every 24 hours and new reviews sent in real time. It also makes clear that the Bazaarvoice contract is yours to acquire directly. So Advanced plus syndication is two commercial agreements, and our Bazaarvoice API and pricing page covers why that second one has no published price either.
Before you pay for the upgrade
Do you actually need the Okendo Merchant API?
Plenty of teams upgrade for the API and then use it for one job an existing connector already did. These are the cases where it is genuinely required, and the ones where it is not.
You need it
Data leaving Okendo
Every review, including pending and rejected ones, going into a warehouse or BI tool on a schedule. Moderation from an internal tool. Loyalty balances adjusted from a system Okendo has no connector for. These need authenticated write or full read access, and the Storefront API cannot provide either.
You probably do not
Showing reviews somewhere new
A headless storefront, a mobile app or a page off Shopify that needs published reviews. The Storefront REST API reads those on any plan with no key. Okendo also documents widget installs for headless builds and Shopify Hydrogen, which may save writing the rendering yourself.
Try this first
Shopify Flow and connectors
Okendo says merchants on all plans can integrate through Shopify Flow, provided they have access to Flow, which covers custom loyalty earn rules without a key. The Shopify listing names Klaviyo, Gorgias, Postscript, Meta and TikTok as integrations. Check these before you buy an API to reproduce one.
Honest positioning
Product reviews on the SKU, business reviews on the store
We sell review software, so read this as an interested opinion. It is still the split we would give a friend running a Shopify brand.
Okendo is for reviews of what you sell
Star ratings and photo reviews on each product page, review request emails after delivery, Q&A, loyalty and referrals on one bill. On Shopify it is a strong choice with 1,422 reviews and a 4.8 rating on its app listing when we checked. Nothing we make replaces product reviews on a SKU, and if that is the job, Okendo or a peer like Yotpo is the right purchase.
We are for reviews of who you are
A new visitor on your homepage, cart or wholesale page is asking whether the company is trustworthy, and the answer lives on Google, Trustpilot and G2, not in product stars. Okendo does not pull those in. We collect, monitor and display Google, G2, Trustpilot and direct reviews in one widget, with no API key, no plan gate on the display and flat pricing from $24 a month billed yearly.
Plenty of brands run both. If that is you, see how Google reviews on a Shopify store sit alongside a product review app without clashing.
Questions people actually search
Okendo API questions, answered
Keep reading
Related review API and pricing pages
Okendo pricing
Every published plan by order band, the annual discount, Loyalty and bundle pricing, and the Advanced tier Okendo never prices.
Yotpo API pricing
The closest Shopify peer, with a published five requests per second ceiling and a key any administrator can create.
Bazaarvoice API pricing
The enterprise end of the category and the network Okendo syndicates into: no published price, no published rate limit.
Yotpo alternatives for Shopify
What Okendo, Loox and Judge.me charge against Yotpo, and which one fits a store at your order volume.
Google reviews on Shopify
Put your store's Google rating on the homepage and cart, next to whatever product review app you already run.
Review API pricing compared
Google, Yelp, Trustpilot and G2 priced at source, with what each one returns per business.
Store level reviews on your site without a plan upgrade
Google, G2, Trustpilot and direct reviews in one widget, with collection sequences that grow the number you have. Flat pricing from $24 a month, published.
From $24/mo, billed yearly. No per-review fees.