The Beauty API contains around 180,000 products from more than 24,000 stored brand names. Skincare accounts for 58% of the catalogue, followed by haircare, body and bath, suncare and makeup. This guide explains what those totals mean for a beauty app, where coverage is limited, and how to check the brands you need before buying.
Data basis: Updated as at 15 October 2026. See the changelog for released changes.
What categories does the beauty product dataset cover?
| Category | Rounded share | Products in the API build |
|---|---|---|
| Skincare | 58% | 103,629 |
| Haircare | 13% | 23,121 |
| Body and bath | 10% | 17,641 |
| Suncare | 8% | 14,628 |
| Makeup | 8% | 14,490 |
| Other, fragrance and uncategorised | 3% | 5,657 |
The skincare subset is the largest starting point for ingredient lookup and product filtering. Haircare and body care are also substantial.
Check your brands before choosing a dataset
Start with the brand coverage checker on the Complete Archive page. Enter a brand to see an approximate product count.
For a reliable purchasing decision, make a short list of the exact products your users need. Check their names, formulations and ingredient lists as well as the number of records returned.
If you are choosing between providers first, our beauty products dataset comparison covers that decision. This page is specifically about evaluating our catalogue.
Which beauty brands are included?
These are the eleven largest stored brand names by product count in the measured API build:
| Stored brand name | Products |
|---|---|
| Nivea | 1,209 |
| L'Oreal Paris | 1,065 |
| Garnier | 977 |
| Revolution | 814 |
| Neutrogena | 794 |
| Balea | 789 |
| Dove | 719 |
| Bielenda | 672 |
| Isana | 656 |
| innisfree | 613 |
| La Roche-Posay | 606 |
Country coverage: headquarters is different from availability
The origin field identifies a brand's headquarters country. It does not tell you where a product is sold, manufactured or currently in stock.
| Brand headquarters | Products with that origin |
|---|---|
| USA | 23,420 |
| South Korea | 14,045 |
| France | 9,150 |
| Germany | 7,845 |
| United Kingdom | 5,987 |
| Poland | 3,821 |
| India | 2,913 |
| Japan | 1,791 |
| Italy | 1,599 |
| Indonesia | 1,586 |
| Australia | 1,547 |
| Spain | 1,397 |
| Canada | 1,244 |
| Netherlands | 790 |
| Sweden | 693 |
| Hungary | 618 |
What ingredient data comes with a product?
Products link to an ingredient dictionary and preserve ingredient order. Additional fields include functions, chemical identifiers and editorial or ingredient-level ratings where populated. These fields are not complete for every ingredient.
In the measured API build, functions are populated on about 94% of product–ingredient links, CAS numbers on 86%, EC numbers on 75% and editorial ratings on 33%. These are occurrence-weighted rates: a common ingredient counts each time it appears in a product.
See the API documentation for fields and plan access.
Questions to settle before buying
Can I request a missing brand? Yes. Send your list to support for a coverage check and discussion of gaps. Confirm any delivery commitment before making it a dependency of your launch.
Will API and dataset counts always match? No. Dataset purchases are release snapshots; the API can receive intervening patches. Confirm the version used for a quoted coverage count.
What should I send for a useful coverage check? Brand, product name, target market and a source link or barcode where available. That makes it easier to distinguish a missing record from a different spelling or formulation.
Start with the coverage checker, then inspect the records that matter to your app. A small, representative acceptance list is a better buying test than any headline catalogue total.