Content APIs for categories, attributes, and products
You can now browse the noon category tree, discover exactly which attributes a category expects, submit products against it, and read back their content — four endpoints, with a guide set that takes you from first call to go-live.
| Endpoint | Summary |
|---|---|
POST /v1/categories/list | ListCategories — lists all available product categories in the catalog. |
POST /v1/categories/attributes/list | ListCategoryAttributes — retrieves the attributes for a specified product category. |
POST /v1/product/upsert | UpsertProduct — creates or updates a product in the catalog. |
POST /v1/product/content/get | GetContent — retrieves content information for specified products. |
Guides
Five documents walk through a first integration end to end:
- Content API overview — how the service fits into the catalog lifecycle
- Quickstart — your first successful call
- Discover category attributes — find out what a category requires before you submit
- Submit a product — build and send a valid product payload
- Track and fix — read back content status and correct rejections
- Go live — the checklist before you move to production
The published reference is the source of truth for these endpoints: field and enum names match the service exactly, and rate limits render from the live specification.