The feed format
A connected collection is one JSON file on your site. Historic Thread fetches it on a schedule, gives each garment a thread, and links back to you. It is the same format FashionablyGood publishes; copy it.
Publish
Put the file anywhere on your domain, for example https://yourshop.com/feed/threads.json, and tell us the URL. We fetch it hourly. An RSS version is welcome but optional.
Example
{
"site": "Your Shop Name",
"generated": "2026-10-21T19:00:00Z",
"items": [
{
"code": "YS-1042",
"title": "Halston Ultrasuede Shirt Dress",
"brand": "Halston",
"era": "1970s",
"size": "8",
"color": "camel",
"category": "dresses",
"description": "Halston's signature Ultrasuede, 1975, with the original belt.",
"status": "available",
"url": "https://yourshop.com/products/halston-ultrasuede-1042",
"images": ["https://yourshop.com/img/1042-1.jpg"],
"chapters": [
{"key": "label", "when": "The label", "title": "Halston", "body": "Roy Halston Frowick, New York, 1968 to 1984."},
{"key": "received", "when": "Received", "title": "March 2026", "body": "From an estate in Lake Forest, Illinois."},
{"key": "worn", "when": "Worn 1978", "title": "A wedding in Chicago", "body": ""},
{"key": "today", "when": "Today", "title": "For sale", "body": ""}
],
"created_at": "2026-03-04 10:12:00",
"updated_at": "2026-10-20 15:40:00"
}
]
}
Fields
code (required) — your stable ID for the piece. It becomes the thread's address, /t/CODE, so never reuse one. Letters, digits and dashes.
title (required) — what you'd call the piece.
brand, era, size, color, category — free text; category from dresses, suits, outerwear, separates, shoes, jewelry, bags, accessories, other.
status — available, sold, rented, kept. Retired pieces: just leave them out of the file and the thread stays, marked as no longer listed.
url — your listing. Every thread links back to it.
images — full URLs, first one is the cover.
chapters — the thread itself, in order. Each has a key (label, made, received, worn, altered, cleaned, sold, rented, today, or your own), a short when, a title, and an optional body.
created_at, updated_at — so newest-first works.
Rules of the record
Only publish what you would print on a hang tag. No customer names without consent, no prices paid to you, nothing you'd be unhappy to see on a public page in ten years. Threads are permanent by design.
Reading the database
Every thread page is also available as JSON at /t/CODE.json, and the whole database at /threads.json. Free, no key, please cache and credit.
Questions, or want to connect something that doesn't fit this shape? Write to us.