Data model
Recipes
A user-authored bread recipe in the personal recipe library. Carries identity (name, blurb, difficulty), totals (flour, total, unit/unitPl), an optional hero image, and the two free-form working lists ingredients and phases that drive the guided bake flow.
bread_recipe200Fields
Per-field validation rules. Values that violate any constraint are rejected with 400 before they reach the database.
| Field | Type | Constraints |
|---|---|---|
| diff | max length 32 | |
| hero | string | max length 200 |
| name | string | max length 200 |
| unit | string | max length 32 |
| blurb | string | max length 2000 |
| flour | string | max length 64 |
| total | string | max length 64 |
| phases | list | - |
| unitPl | string | max length 32 |
| ingredients | list | - |
Mutability
Which fields can you send, and when? Anything without a marker is server-managed - sending it isn't an error, it's silently ignored.
| Field | Create | Patch |
|---|---|---|
| diff | ||
| hero | ||
| name | ||
| unit | ||
| blurb | ||
| flour | ||
| total | ||
| phases | ||
| unitPl | ||
| ingredients |
Fields marked create-only but not patchable are immutable after creation. Server-managed fields include id, timestamps, ownership, and status.
Filtering & sorting
Combinable on list endpoints. Repeating a filter key produces an IN clause; prefixing a sort key with - reverses direction. Example: ?status=open&status=blocked&sort=-created_at.
Filter keys
data__namedata__diffstatusis_archivedowned_bySort keys
created_atupdated_atdata__nameDefault: name
Endpoints
Each endpoint below lists its HTTP method, path, and the PAT scope it needs. Code samples cover curl, JavaScript, TypeScript, Python, Rust, Java, and WebSocket.
/xapi2/data/bread_recipebread_recipe:listList objects
Returns a paginated list of objects you can read. Default page size is 20; pass ?limit= to change (capped per type). Use ?after=<id> for keyset pagination on created_at-sorted lists, or ?offset= for offset paging.
curl -H "Authorization: Bearer pat_…" \"https://sourdoughtracker.com/xapi2/data/bread_recipe?limit=20"
/xapi2/data/bread_recipe/{id}bread_recipe:readRead one
Returns the object by id. 404 if it does not exist or you cannot read it (the two cases are intentionally conflated).
curl -H "Authorization: Bearer pat_…" \https://sourdoughtracker.com/xapi2/data/bread_recipe/OBJECT_ID
/xapi2/data/bread_recipebread_recipe:createCreate
Creates a new object. Body is a flat JSON dict of field values. Server-side fields (id, timestamps, ownership) are filled automatically; only fields listed below as creatable are read from the body.
curl -H "Authorization: Bearer pat_…" \-H "Content-Type: application/json" \-X POST https://sourdoughtracker.com/xapi2/data/bread_recipe \-d '{"name": "…"}'
/xapi2/data/bread_recipe/{id}bread_recipe:updateUpdate
Partial update. Only fields included in the body are touched; everything else is preserved. Same allow-list as create, minus the fields that are immutable post-create.
curl -H "Authorization: Bearer pat_…" \-H "Content-Type: application/json" \-X PATCH https://sourdoughtracker.com/xapi2/data/bread_recipe/OBJECT_ID \-d '{"name": "…"}'
/xapi2/data/bread_recipe/{id}bread_recipe:deleteDelete
Removes the object. It vanishes from every default list immediately and stops being returned by read / list.
curl -H "Authorization: Bearer pat_…" \-X DELETE https://sourdoughtracker.com/xapi2/data/bread_recipe/OBJECT_ID
Use in CLI
The same endpoints are also exposed via the Sourdough Tracker CLI. For scripts, CI, and bulk imports it's usually the faster path.
sourdoughcli bread_recipe list --limit 5sourdoughcli bread_recipe get <id>sourdoughcli bread_recipe create --name "Hello"sourdoughcli bread_recipe upsert --unique name --csv items.csvsourdoughcli bread_recipe schema # fields & limits
Full command reference, profiles, CSV import, auto-retry, NDJSON streaming → /docs/cli