Category references

These read-only endpoints expose the house’s existing item categories. They require categories.read.

Paths are relative to /api/v2. All results belong to the API key’s house.

{
  "id": "cat_b48e0a19-5c72-4d83-91af-3e6b2c07d514",
  "name": "Silver",
  "slug": "silver",
  "parent": null,
  "created_at": "2026-05-20T14:02:00Z",
  "updated_at": "2026-07-05T19:08:11Z"
}

name uses the house’s default language; a missing translation returns null. parent is another category’s public ID or null. A parent outside the house is never exposed.

Find a slug

Request /api/v2/categories?slug=silver. Matching is exact and case-sensitive; values are not trimmed. Empty or whitespace-only strings, NUL bytes, arrays and objects are rejected.

Slugs are not unique. Follow pagination through every match and resolve ambiguity explicitly. Both endpoints use the standard data envelope. The list also supports limit and cursor; cursors belong to their original house and filters. Show rejects collection filters, and neither endpoint supports expansions.

A record without a valid public identity returns a 500 Problem Details response. Reads never repair stored identities. Creating categories and assigning them to items remain future API work; the broader taxonomy plan describes that direction.