Discover/Fragrantica API
live

Fragrantica APIfragrantica.com

Access Fragrantica perfume data via API: search perfumes, get fragrance notes pyramids, main accords, ratings, brand lists, and note categories.

Endpoint health
verified 1d ago
list_notes
get_perfume_details
list_brands
search_perfumes
4/4 passing latest checkself-healing
Endpoints
4
Updated
21d ago

What is the Fragrantica API?

The Fragrantica API covers 4 endpoints that expose perfume search, detailed fragrance profiles, brand directories, and note categories from Fragrantica's community-driven perfume database. The get_perfume_details endpoint alone returns 8 distinct fields including the full notes pyramid (top, middle, and base), main accords with intensity scores, average rating, and a description — giving developers structured access to data that typically requires manual browsing.

Try it
Page number (0-based)
Results per page (max 100)
Search keyword (e.g. 'chanel', 'rose', 'dior')
api.parse.bot/scraper/d2c369a4-db4f-46ae-829d-562361126109/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/d2c369a4-db4f-46ae-829d-562361126109/search_perfumes?page=0&limit=5&query=rose' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace fragrantica-com-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Walkthrough: Fragrantica SDK — search perfumes, browse brands & notes."""
from parse_apis.fragrantica_perfume_api import Fragrantica, Letter, PerfumeNotFound

client = Fragrantica()

# Search for perfumes matching a keyword, capped at 5 results.
for perfume in client.perfumes.search(query="oud", limit=5):
    print(perfume.naslov, perfume.dizajner, perfume.rating)

# Get detailed info for one perfume via its URL.
detail = client.perfumedetails.get(url="https://www.fragrantica.com/perfume/Chanel/Chanel-No-5-Eau-de-Parfum-40069.html")
print(detail.name, detail.brand, detail.rating_value)
print("Top notes:", detail.notes.top)
for accord in detail.main_accords:
    print(f"  {accord.name}: {accord.intensity}")

# Handle a missing perfume gracefully.
try:
    client.perfumedetails.get(url="https://www.fragrantica.com/perfume/Unknown/Fake-99999999.html")
except PerfumeNotFound as exc:
    print(f"Not found: {exc}")

# List brands starting with a specific letter using the Letter enum.
for brand in client.brands.list(letter=Letter.D, limit=5):
    print(brand.name, brand.url)

# Browse fragrance note categories.
for category in client.notecategories.list(limit=3):
    print(category.category, [n.name for n in category.notes[:3]])

print("exercised: perfumes.search / perfumedetails.get / brands.list / notecategories.list")
All endpoints · 4 totalmissing one? ·

Full-text search over Fragrantica's perfume database via Algolia. Returns paginated results with perfume name, designer, year, rating, gender, and thumbnail. The API key is fetched dynamically from the site on first call.

Input
ParamTypeDescription
pageintegerPage number (0-based)
limitintegerResults per page (max 100)
queryrequiredstringSearch keyword (e.g. 'chanel', 'rose', 'dior')
Response
{
  "type": "object",
  "fields": {
    "hits": "array of perfume objects with naslov (name), dizajner (designer), godina (year), rating, slug, id, spol (gender), thumbnail",
    "page": "integer current page number",
    "nbHits": "integer total number of matching perfumes",
    "nbPages": "integer total number of pages",
    "hitsPerPage": "integer results per page"
  },
  "sample": {
    "data": {
      "hits": [
        {
          "id": 40069,
          "slug": "Chanel/Chanel-No-5-Eau-de-Parfum",
          "spol": "female",
          "godina": 1986,
          "naslov": "Chanel No 5 Eau de Parfum",
          "rating": 3.5883,
          "dizajner": "Chanel",
          "thumbnail": "https://fimgs.net/mdimg/perfume/m.40069.jpg"
        }
      ],
      "page": 0,
      "nbHits": 391,
      "nbPages": 20,
      "hitsPerPage": 20
    },
    "status": "success"
  }
}

About the Fragrantica API

Search and Browse Perfumes

The search_perfumes endpoint accepts a query string (e.g. 'chanel', 'rose', 'oud') and returns paginated results via 0-based page and limit parameters. Each hit includes naslov (perfume name), dizajner (designer), godina (year), rating, spol (gender classification), slug, id, and a thumbnail URL. The nbHits field tells you the total match count so you can calculate pagination depth using nbPages and hitsPerPage.

Detailed Perfume Profiles

The get_perfume_details endpoint takes a full Fragrantica perfume URL and returns the complete fragrance profile. The notes object contains three keyed arrays — top, middle, and base — each listing note names. The main_accords array returns objects with name and intensity, which lets you rank a perfume's dominant character (e.g. woody at 85, floral at 60). rating_value and rating_count reflect community scoring, and description provides the editorial text for the fragrance.

Brands and Notes Directories

list_brands accepts an optional letter parameter (single character A–Z) to filter results alphabetically, returning brand name and Fragrantica url for each match. This makes it straightforward to build or refresh a full brand index letter by letter. list_notes requires no parameters and returns every fragrance note grouped into categories (e.g. Citrus, Flowers, Woods), with each note's name, url, and image field — useful for building note-based search interfaces or ingredient taxonomy trees.

Reliability & maintenanceVerified

The Fragrantica API is a managed, monitored endpoint for fragrantica.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when fragrantica.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official fragrantica.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Last verified
1d ago
Latest check
4/4 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Build a fragrance recommendation engine using main_accords intensity scores and note pyramid data
  • Index a full brand directory by iterating list_brands through letters A–Z
  • Populate a perfume database with year, gender, rating, and thumbnail from search_perfumes hits
  • Display a visual notes taxonomy using the categorized output of list_notes with note images
  • Compare community ratings across multiple perfumes using rating_value and rating_count
  • Filter a perfume catalog by gender classification using the spol field from search results
  • Enrich an e-commerce fragrance catalog with top/middle/base note pyramids via get_perfume_details
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min

One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does Fragrantica offer an official developer API?+
Fragrantica does not publish an official public developer API or documented data access program. This Parse API provides structured access to the data available on fragrantica.com.
What does `get_perfume_details` return that `search_perfumes` does not?+
search_perfumes returns lightweight metadata: name, designer, year, rating, gender, slug, and thumbnail. get_perfume_details adds the full notes pyramid (top, middle, base arrays), main_accords with intensity values, a full description text, and explicit rating_count. You need to call get_perfume_details with a perfume's URL to get the notes and accords data.
Can I retrieve user reviews or individual community votes for a perfume?+
Not currently. The API returns rating_value (average score) and rating_count (number of votes) but does not expose individual user reviews or vote breakdowns. You can fork this API on Parse and revise it to add an endpoint that returns per-user review text and scores.
How does pagination work in `search_perfumes`?+
Pagination is 0-based: pass page=0 for the first page. The response includes nbHits (total results), nbPages (total pages), and hitsPerPage to let you calculate how many pages exist for a given query. Increment page up to nbPages - 1 to walk through all results.
Does the API cover fragrance concentration variants (EDP, EDT, parfum)?+
Concentration variant data (e.g. Eau de Parfum vs. Eau de Toilette) is not a dedicated field in any current endpoint response. The search_perfumes hits and get_perfume_details response do not explicitly expose concentration as a structured field. You can fork this API on Parse and revise it to parse and surface concentration information from perfume detail pages.
Page content last updated . Spec covers 4 endpoints from fragrantica.com.
Related APIs in EcommerceSee all →
fragrantica.it API
Search for perfumes and retrieve detailed information including fragrance notes, accords, olfactory family, perfumer, year of release, and community ratings from Fragrantica.
selfridges.com API
Search and browse Selfridges fragrance products by keyword, category, or brand. Returns detailed product data including fragrance notes, scent tags, pricing, sizing, and product descriptions.
sephora.com API
Search and browse Sephora's product catalog to find detailed information about beauty items, including specifications, customer reviews, Q&A discussions, pricing, and real-time availability. Filter products by category or brand, and access comprehensive brand listings to discover exactly what you're looking for.
ecco-verde.it API
Browse and search the Ecco Verde natural beauty catalogue. Retrieve full product details including ingredients (INCI), variants, and attributes; search by keyword; explore products by category or brand; and fetch personalised product recommendations.
natura.com.br API
Browse Natura's complete product catalog, search for items by category or keyword, and retrieve detailed product information including prices, descriptions, ingredients, and customer reviews. Supports category navigation, faceted filtering, and paginated search results.
incidecoder.com API
Search cosmetic products and ingredients, get detailed analysis of their safety and composition, and decode ingredient lists to understand what's in your beauty products. Find similar products and explore comprehensive ingredient databases to make informed decisions about the cosmetics you use.
knowde.com API
Search and retrieve detailed information about chemical products, ingredients, suppliers, and brands available on the Knowde marketplace. Find specific formulations, documents, and supplier storefronts across various industries and product categories to discover suppliers and sourcing options.
theordinary.com API
Browse and search The Ordinary's complete product catalog by category or ingredients. View detailed product information including formulas and key actives, apply filters by product type, concern, or ingredient, and read customer reviews to compare and evaluate products.