One product id, thirty storefronts, thirty prices

Pass country on any call — search, category, detail, batch_detail or reviews all take it, and it defaults to US. Thirty storefronts are supported: US, CA, MX, BR, GB, DE, FR, IT, ES, NL, PL, SE, TR, UA, IL, AE, SA, ZA, IN, JP, KR, HK, TW, SG, MY, TH, VN, PH, AU and NZ. Every response repeats the country and the ISO currency it was priced in, so a stored row can never lose track of which storefront it came from. If a storefront cannot be reached for a request, the call fails with a clear error instead of quietly answering from a different country — a price in the wrong currency is worse than no price.

That is what price_by_country does. Give it a product id and up to twelve country codes and it returns one row per storefront with the price, the ISO currency, the local display price, the stock state and whether the product is listed there at all. Products are not on every storefront — when one is missing, that row says so rather than being dropped, so you can see where a product is simply not sold. No currency conversion is applied anywhere in this API: each figure is the number iHerb itself prints in that market, because an FX rate we invented would be the least reliable number on the page.

Real reviews, and no account is involved in reading them. Each page returns ten with the review text, the title, the star rating, the date, the language, the verified-purchase flag, the helpful-vote counts and how many photographs are attached. Alongside them you get the average, the total, and the full per-star breakdown — for product 468 that is 6,580 ratings split 5,314 five-star, 871 four, 305 three, 52 two and 38 one — plus iHerb's own written summary of what customers said. Product 468 runs to 653 pages of reviews. Reviewer display names are withheld by default and returned only if you explicitly ask for them; handles and avatars are never returned.

Every filter this API exposes narrows the result, and we publish the proof. Against an unfiltered 14,940 results for vitamin c: the four-star band returns 8,909, the NOW Foods brand 756, California Gold Nutrition 319, the cheapest price band 248, the immune-support health topic 2,604, the vegan attribute 4,820 and the iTested programme 273. In-stock-only takes 14,940 to 14,468. Two filters that iHerb itself advertises are deliberately not exposed here: one is accepted and changes nothing, and the other returns an error for every value. Rather than pass those through and let you believe they worked, we left them out.

Because it is a band and not a minimum, and the honest name saves you a wrong result. Asking for band 3 returns products rated roughly 2.8 to 3.7 — it excludes the four- and five-star products, rather than including everything above three. Measured on one storefront: band 5 returns 5,818 products rated about 4.8 and up, band 4 returns 8,909 rated roughly 3.8 to 4.7, band 3 returns 36, band 2 returns 6 and band 1 returns 2. The filters action prints the live count sitting behind each band so you can see the shape before you query.

No, and this one surprised us enough to put it in the response. Unsorted, vitamin c returns 14,807 results; sorted by price, by rating, by newest or by any other explicit sort, the same query returns 10,559. Sorting changes which products are in the set by about 29 percent, it does not merely change their order. The search response carries a sorted_population_differs flag so this is visible in the data rather than only in the documentation. Featured and relevance are the two that leave the total alone.

Call the filters action with a keyword or a category slug. It returns iHerb's own vocabulary for that query with a live product count beside every option: 1,056 brands, 1,349 category ids, plus health topics, price bands, programmes and the attribute groups that cover diet and certification, product form, age range and skin or hair concern. That is 28 filter groups and 2,725 options on a single query. The codes are opaque — NOW Foods is NOW, 100% PURE is URE — so reading them from this call is the only reliable way to get them right.

Three ways, and none of them needs you to know an id in advance. Search by keyword; browse a category, with all 1,483 category slugs available from the categories action; or, if you already have an iHerb URL, the id is the last path segment. Search also resolves a SKU or part number directly, so a query that exactly matches a product comes back flagged as an exact match. A search row and a detail record agree: we checked six ids from search through to detail and got the same id, the same type, the same SKU and the same price to the cent on all six.

iHerb API is a ReefAPI endpoint group for supplements and natural health, priced in 30 countries. It returns live JSON through POST requests under /iherb/v1.

Yes. ReefAPI starts with 1,000 free credits, no card required. iHerb calls use the same shared credit balance as every other ReefAPI engine.

No login to iHerb is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.

The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.

iHerb actions currently cost 1-3 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.

Yes. Connect ReefAPI once through MCP and your assistant can call iherb actions with the same key, credit pool and JSON envelope used by normal REST requests.