Old Fashioned Club — Developer documentation
Old Fashioned Club (OFC) is a Paris pre-owned luxury house. Its public REST API exposes the authenticated second-hand catalogue — products, collections, categories, journal and CMS content — so AI agents and integrations can browse stock, prices and editorial content programmatically.
Base URL & authentication
Base URL: https://oldfashionedclub.com/store
Auth: every store route takes the public publishable key in the x-publishable-api-key header. The key is safe to expose client-side; it is scoped to sales channels.
Publishable key: pk_26155904f5eef411385366652b06982d2a4814c8ce3cfc4c2dcde1a439983f89
curl https://oldfashionedclub.com/store/products?limit=5 \ -H "x-publishable-api-key: pk_26155904f5eef411385366652b06982d2a4814c8ce3cfc4c2dcde1a439983f89"
Key endpoints
- GET
/store/productsList in-stock pieces. Filter: ?q=, ?brand=, ?category_id[]=, ?collection_id[]=, ?handle=, ?limit=/&offset=. - GET
/store/products/{id}One product by id (prod_…) — variants, prices, metadata. - GET
/store/collectionsCollections (curated edits). ?handle= for one. - GET
/store/categoriesCategory tree (femme, homme, sacs, bijoux, …). - GET
/store/regionsRegions, countries and currencies (Europe, EUR). - GET
/store/postsJournal articles (guides, maison stories). ?lang=fr|en. - GET
/store/content/pages/{slug}Published CMS pages (legal, about, FAQ). ?lang=fr|en. - POST
/store/cartsCreate a cart; add line items, then complete to order. - POST
/store/offersSubmit a price offer on a one-of-one piece.
The full machine-readable surface — every operation, parameter and response schema — is in the OpenAPI spec.
For AI agents
- Markdown everywhere: send
Accept: text/markdownto any page on this site to get a markdown rendering (404s answer in markdown too). - MCP server:
https://oldfashionedclub.com/mcp/mcp(Streamable HTTP, staff API key) — manifest at /mcp.json. - Errors: JSON everywhere —
{ type, code, message, hint, docs }.
Machine-readable resources
- openapi.json — OpenAPI 3.0 spec of the whole store API
- mcp.json — MCP manifest (server, auth, capabilities)
- llms.txt — Curated map of the site for LLMs
- llms-full.txt — Exhaustive brand/page/article index
- agent.txt — When-to-use guidance + call patterns for agents
- sitemap.xml — All public URLs
Versioning & deprecation policy
The API major version is pinned per deployment (currently 2, the Medusa v2 store API line). Every operation accepts the optional x-api-version header.
Backwards-incompatible changes ship only as a new major version. When an endpoint or field is scheduled for removal it is marked deprecated: true in the OpenAPI spec and announced here at least 90 days before removal; responses then carry Deprecation and Sunset headers (RFC 8594 / RFC 9745). Nothing is currently deprecated.
Questions: [email protected] · +33 6 83 09 50 01 · 4 & 6 rue des Saussaies, 75008 Paris