Bazaarvoice API pricing and cost: Conversations API key, access and documentation
Bazaarvoice publishes no price for the API, and no price for anything else. Its pricing page lists package names and a sales form with no dollar figures on it. There is no free tier, no self serve signup and no numeric rate limit in the public documentation. What Bazaarvoice does document precisely is the part most people get stuck on: a passkey has to be requested in the Portal and then approved by a Technical Administrator, and until someone enables it your key is inactive. Below is every fact Bazaarvoice actually publishes, read at source in September 2026.
No passkey, no approval queue
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.
Business reviews on your own pages in a script tag. We cover Google, G2, Trustpilot and direct reviews. We are not a product review syndication platform, so if you need star ratings on retailer product pages, Bazaarvoice is the right category and this page is here to price it honestly.
The question behind most Bazaarvoice API searches
How much does the Bazaarvoice API cost?
Nobody can tell you, including Bazaarvoice's own website. Read on 9 September 2026, bazaarvoice.com/pricing contains no numerical dollar amounts, no subscription costs and no per unit pricing for any tier. Here is the full map of what is published and what is withheld, so you know exactly which questions to take into the sales call.
| What buyers ask | Published by Bazaarvoice | What you get instead |
|---|---|---|
| Plan prices | No | Package names only, plus "Tell us a little about yourself, and our sales team will be in touch shortly" |
| Which package includes the API | No | A prerequisite in the docs: your account must include the Ratings and Reviews solution assignment |
| Implementation cost | No | "Each package is paired with a recommended implementation service", priced on request |
| API rate limits | No number | An error code, ERROR_REQUEST_LIMIT_REACHED, with no stated ceiling |
| Results per request | Yes | A hard maximum of 100, paged with Offset |
| How to get a key | Yes, in detail | Portal request, then explicit approval by a Technical Administrator |
| Free or trial tier | None exists | API access is switched on for an existing client instance, so a contract comes first |
Every dollar figure you will find for Bazaarvoice online is secondhand. Procurement marketplaces and review aggregators publish ranges collected from buyers, not from Bazaarvoice, and those ranges are wide enough to be useless for budgeting. We are not going to repeat them here as though they were facts. The honest summary is that Bazaarvoice is an enterprise purchase with a negotiated contract, a separate implementation engagement, and modules such as sampling and visual UGC that are quoted on their own. If a number matters to you, the only place it exists is your own quote.
The shape of the contract
What Bazaarvoice actually sells
The pricing page organizes everything into three groups. Knowing which group a capability sits in tells you whether it is part of the reviews contract you are negotiating or a separate module with its own quote.
Source
Getting content created
Sampling, Creator Marketing and Ambassadors. This is where product seeding lives, the programs that put your SKU in a reviewer's hands so a new listing does not launch with zero stars. It is normally quoted separately from the display contract.
Display
Ratings and Reviews
Ratings & Reviews and Social Commerce, each offered as Essentials, Advanced and Enterprise. This is the group that matters for API access, because the documentation names the Ratings and Reviews solution assignment as a prerequisite for a Conversations API key.
Amplify
Insights, AI and Connections
Reporting, the AI features and the retailer connections that carry syndicated content. Support is sold on its own axis as Standard, Priority or Enterprise, which is worth checking before you assume an implementation includes hands on help.
The practical consequence for a developer is that "does Bazaarvoice have an API" and "can I use the Bazaarvoice API" are different questions with different answers. The API exists and is documented publicly. Whether it is enabled on your instance depends on which of these packages your company bought, and that is decided in a contract you probably did not sign. Before you plan a sprint around it, confirm with your account team that API access is switched on, because there is no way to test that from the outside.
Where most integrations stall
How to get a Bazaarvoice API key
This is the part Bazaarvoice documents thoroughly and almost nobody writes about. A passkey is not self issued. You request it, and then a different person has to approve it.
1
Check the prerequisites
Three things have to be true before the request will work: API access must be enabled for your client instance, your Portal account needs the Technical Contributor or Technical Administrator role, and the account must include the Ratings and Reviews solution assignment. Miss any of these and the option is not there to click.
2
Request the key in the Portal
Sign in to the Bazaarvoice Portal, select the client instance you want the key for, then go to Settings and API. Click Request API key, choose Conversations API, and complete the request form. Bazaarvoice notes that any member within a client instance can request keys, so raising the request is not the bottleneck.
3
Get it approved and enabled
This is the bottleneck. In Bazaarvoice's words, requested keys remain inactive until they are explicitly enabled. A Technical Administrator opens the API key management application, filters for keys in Pending state, selects Enable Key and saves. If your key returns an invalid passkey error on day one, this step is usually why.
4
Point it at the right environment
Staging and production are separate hosts with separate keys. Build and test against stg.api.bazaarvoice.com, then swap both the host and the passkey when you promote. Submitting test content against production is the mistake that puts fake reviews on live product pages, and it is not trivially reversible.
Plan for the approval to take days rather than minutes, especially in a large organization where the Technical Administrator sits in another team. It is worth finding out who holds that role before you file the request. This is also the reason a Bazaarvoice integration is a poor fit for a quick proof of concept: you cannot get a working key over a lunch break the way you can with most review APIs, and there is no sandbox you can reach without a contract behind it.
Bazaarvoice API documentation
Which Bazaarvoice API do you actually need?
People search for the Bazaarvoice API as though there is one. There are several, and picking the wrong one costs a sprint. This is the family as documented at developers.bazaarvoice.com.
| API | What it is for | Reach for it when |
|---|---|---|
| Conversations API (CV2) | Retrieve and submit user generated content | You need reviews, questions or answers in or out. This is the default answer. |
| Conversations API (Agrippa/PRR) | The equivalent for PRR customers | Your instance is on the PRR platform. The reference is a separate set of docs, so check which one you are reading. |
| Response API | Create, read, update and delete responses to reviews | You want replies posted from a helpdesk or CX tool rather than the Bazaarvoice interface. |
| Authentic Discovery API | In Bazaarvoice's words, "Enable AI search bots and LLMs to discover your UGC" | You care whether ChatGPT and other answer engines can see your review content, not just shoppers. |
| Product Sentiments API | Sentiment extracted from review content | You want themes and sentiment without building your own NLP over raw review text. |
| Privacy API | Fits Bazaarvoice into your privacy compliance workflow | You have to service deletion and access requests across systems. |
| Transactions, Notifications, Social Commerce Display | Post purchase triggers, event callbacks and social display | You are wiring review requests to orders or rendering visual UGC. |
Conversations API in practice
How a Bazaarvoice review request is built
Display calls are plain GET requests with the credential in the query string. There is no OAuth dance, which makes the first call easy and the security model something you have to think about.
The two hosts
Staging is stg.api.bazaarvoice.com/data/ and production is api.bazaarvoice.com/data/. Reviews come from the reviews.json resource, and you pin the contract with an apiversion parameter, commonly apiversion=5.4. Keep the version pinned in code rather than tracking whatever is newest, because response shapes have changed across versions.
The parameters that matter
- passkey, your approved key, passed in the query string.
- Limit, the count of results returned, to a documented maximum of 100.
- Offset, which identifies the position within the total result to start returning results.
- Filter, written as Attribute:operator:Value, with eq, neq, gt, lt, gte and lte available. A filter with no operator is treated as if eq had been used.
- Sort, written as Attribute:asc or Attribute:desc, with multiple attributes separated by commas.
The 100 result ceiling changes your architecture
A catalog with 200,000 reviews is 2,000 requests at best, and that is before filtering. Because no rate limit is published, you cannot calculate in advance how long a full backfill takes or whether it will trip a throttle you have not been told about. The safe pattern is an incremental sync keyed on a date attribute, run on a schedule, with generous backoff, rather than a nightly full crawl.
Bazaarvoice is explicit that pagination has an intended use and warns that any other usage will cause performance degradation and may result in restrictions or limitations on API usage. Treat that as a real constraint. Deep offsets across a large catalog are exactly the pattern it is warning about, and the consequence is a conversation with your account team rather than a clean error.
One more thing worth knowing before you design a front end around it: a display passkey travels in the URL, so it is readable by anyone who views source on your page. That is by design for display use, but it means the passkey is not a secret and should never be the only thing standing between the public and a submission endpoint.
The quirk that breaks first integrations
Bazaarvoice always returns HTTP 200, even when it failed
This single sentence in the troubleshooting documentation invalidates the error handling in most HTTP clients, and it is the reason a call can look successful while returning nothing.
In Bazaarvoice's own words: "The Conversations API always returns an HTTP 200 code, even when an error has occurred. If there is an error, we will include it in the body of the response." So a client that checks the status code and moves on will record a failed call as a success, log nothing, and quietly write empty results into whatever it feeds. Parse the body and check the Errors array on every single response, including the ones that look fine.
| Error code | Documented meaning | What it usually is in practice |
|---|---|---|
| ERROR_PARAM_INVALID_API_KEY | "The passkey provided is invalid." | The key was requested but never enabled, or you are using a staging key against production. |
| ERROR_UNSUPPORTED | "Feature is not supported for the client" | Your contract does not include that capability. This is a commercial answer wearing a technical error code. |
| ERROR_REQUEST_LIMIT_REACHED | Rate limiting, too many requests per time interval | You are backfilling too aggressively. No public number tells you where the line is, so back off and slow down. |
| ERROR_NOT_FOUND | "404 - Request not found" | A malformed resource path, or a product identifier that exists in your catalog but not in the Bazaarvoice one. |
The distinction between the first two is the one to internalize. An invalid passkey is something you can fix yourself by chasing an approval. ERROR_UNSUPPORTED cannot be fixed in code at all, no matter how the request is written, because it is your contract answering. Recognizing which one you are looking at saves a week of debugging a request that was never going to work.
Honest positioning
When Bazaarvoice is right, and when it is the wrong category
We sell review software, so treat this as an interested opinion. It is still the split we would give a friend, and it saves people from buying the wrong shape of product.
Buy Bazaarvoice when you need product reviews
Star ratings per SKU, photo and video content on product pages, and syndication of your reviews out to retailer product pages such as Walmart, Target and Home Depot. If your KPI is conversion rate on a product detail page, or coverage of reviews across a retail network you sell through, this is the category and Bazaarvoice is one of the two or three serious names in it. Nothing we make replaces that.
The sampling side matters here too. Seeding a newly launched SKU so it does not sit at zero reviews is a genuinely hard problem, and it is bought as its own module.
You may only need business reviews
A lot of teams arrive at an enterprise UGC quote when what they actually need is reviews about the company: Google, G2, Trustpilot and direct testimonials, collected steadily and shown on marketing pages. That is a different product with a different price, and it does not involve a passkey, an approval queue or an implementation engagement.
That is what we do. We collect, monitor and display Google, G2, Trustpilot and direct reviews through one embeddable widget, and we run the request sequences that grow how many reviews you have in the first place. Flat pricing from $24 a month, published on the page, no sales call required to see it.
Questions people actually search
Bazaarvoice API questions, answered
Keep reading
Related review API and pricing pages
Yotpo API pricing
The other ecommerce UGC API, with a published five requests per second ceiling and a client credentials flow you can complete yourself.
Yotpo vs Bazaarvoice
Retail syndication, sampling and what each vendor will and will not put a number on before a sales call.
Review syndication cost
What syndication to Walmart and other retailers actually costs, and the exclusivity rule that decides your vendor for you.
Review API pricing compared
Google, Yelp, Trustpilot and G2 priced at source, with what each one returns per business.
Trustpilot API
The add-on that sits on a $319 a month floor, the public and private split, and the 100,000 record ceiling.
G2 API pricing
Why the G2 reviews read API is marked in the Enterprise column alone, and what the other tiers actually get.
Business reviews on your site without an approval queue
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.