Put your house on Fraghab.
Collectors have already built pages for your fragrances here, and nobody from your house has checked them. Claim them, correct what is wrong, and see how many people own and wear your work.
- See the entries your customers already published under your brand
- Correct the notes, perfumer credits and release years, and add your own imagery
- Read your own audience numbers: collectors, wearings, and what they want next
- All of it from a sign-in, with no developer and no integration
A verified catalog
Your fragrances appear in Fraghab's member database, brand hub, perfumer pages, and search — with a verified badge collectors trust.
- Name, notes, accords, category, season, and more
- Collectors import your data with one click
- Your entries are never modified by users
Your press kit, rendered
The same key delivers your media. Logo, perfumer portraits, and official bottle imagery each render on Fraghab's public pages the moment they land.
- Your logo on your brand hub
- Perfumer portraits, credited to your house
- Official product shots on library and catalog cards
One simple API
Plain REST JSON with bearer auth. List, create, update, and retire fragrances, and upload media — no SDK, no ceremony.
- GET · POST · PUT · DELETE /api/v1/fragrances
- Media endpoints for logo, portraits, and imagery
- A worklist endpoint shows which portraits are missing
Apply
Fill out the short application at the top of this page. It takes about two minutes.
Verify your brand
Apply from an address at your own domain and you verify yourself by email, in a minute, with no review. Anything else we check by hand within 1 to 2 business days.
Open your console
We email you a link. Set a password and your console opens, with your catalog and your numbers already in it.
Anything you publish appears in the catalog immediately. Your API key sits in the console for whenever your developers want it, and you can rotate or revoke it yourself without asking us.
Brand-locked keys
Every key is scoped to a single brand. All reads and writes are checked against it — no cross-brand access, ever.
Shown once, stored hashed
Your key is displayed exactly once and stored only as a SHA-256 hash. A lost key is reissued rather than recovered, and you can do that yourself from the console.
Generous rate limits
300 reads, 60 writes, and 20 media uploads per key per minute — plenty for a full catalog sync.
Media up to 4 MB
Send jpeg, png, webp, or gif up to 4 MB. We convert everything to webp and serve it cached from the CDN.
Credit every nose
The perfumer field takes an array — ["Anne Flipo", "Dominique Ropion"] — so multiple perfumers are credited unambiguously.
Live immediately
Submissions appear in the member database, and collectors import them with the verified badge attached.
No developer needed
Once you are verified, signing in gives your brand team everything: the entries your customers built, your own audience numbers, and your media. Nobody has to write any code, and nothing goes public until you say so.
- A claim queue listing every entry under your brand that no house owns yet
- Inline editing, plus a draft mode and a preview link for whoever signs off your copy
- Spreadsheet import that shows you the exact changes before it writes any of them
- Drag-and-drop logo and product shots
- Issue a read-only key to your agency instead of sharing your own
The claim queue
Every fragrance published under your brand that no house stands behind, ordered by how many people collect it, each one listing exactly what is missing.
Your audience
Collectors, bottles, wearings and wishlist demand for your house. Aggregate only, and never shown at all below five members.
Draft and preview
Work on copy privately, then send a link to whoever approves it. They need no Fraghab account, and nothing is public until you publish.
Import your spreadsheet
Upload a CSV, match your columns, and see the exact before and after for every row before a single change is written.
Plain JSON, one key
Authenticate with your brand-locked key and manage your whole presence — catalog and media alike. If you can send a curl request, you can be live today.
- GET · POST /api/v1/fragrances, GET · PUT · DELETE /api/v1/fragrances/:id
- POST /api/v1/fragrances/:id/image — official product imagery
- PUT /api/v1/house/logo and PUT /api/v1/perfumers/:name/portrait — your media kit
- GET /api/v1/house and GET /api/v1/perfumers — your account and portrait worklist
- Duplicate detection by name and brand returns the existing record
$ curl -X POST \
https://fraghab.com/api/v1/fragrances \
-H "Authorization: Bearer fh_xxxxxxxxxxxx" \
-H "Content-Type: application/json" \
-d '{
"name": "Oud Wood",
"brand": "Tom Ford",
"category": "EDP",
"notes": ["oud", "sandalwood", "vanilla"],
"perfumer": ["Your Perfumer"]
}'
201 Created
{ "id": "frag_01jw…", "verified": true }
No developer needed
Drop a ready-made skill into Claude Code or OpenAI Codex and just say “sync our catalog to Fraghab” — your assistant handles the API for you.
- Your key lives in an environment variable you set once
- The skills refuse to write your key into any file
- Templates only — no credentials inside the download
A ready-made skill for Anthropic's Claude Code. Unzip it and your assistant knows every endpoint, limit, and flow.
- Catalog sync, imagery, logo, and perfumer portraits
- Reads your key from an environment variable only
- Worked examples and the full endpoint reference
Unzip into ~/.claude/skills, then set FRAGHAB_HOUSE_API_KEY in your shell.
The same capability for OpenAI's Codex — and the bundled OpenAPI spec imports straight into a custom GPT.
- Catalog sync, imagery, logo, and perfumer portraits
- Includes the Codex sandbox setup step for your key
- OpenAPI 3.1 spec doubles as a ChatGPT Action
Unzip into ~/.agents/skills, then set FRAGHAB_HOUSE_API_KEY in your shell.
Ready to put your house in front of collectors?
The application takes about two minutes. Apply from an address at your own domain and you can be in your console a minute later.