sourdough
Sourdough Tracker
A focused sourdough tracker. Keep one record per starter; log every feed, bake, and milestone in one continued journal per starter. Share a single starter's journal with a co-baker.
Base URL
https://sourdoughtracker.comThree ways to connect to Sourdough Tracker - same data, same access rules, different path depending on the job.
Usage & billing
Fair API usage within the published rate limits is included on every plan - the integration shouldn't feel artificially constrained just because you're on a smaller tier. Enterprise customers get bespoke limits on request.
On-demand service is available, and our developer team builds custom integrations on request - reach out if your use case needs more than the standard hookup.
Quick start
- 1
Create a token
Open the Integrations menu in Sourdough Tracker, click *New token*, pick a name + scopes, and copy the
pat_…secret. It's shown exactly once. - 2
Make your first request
Pass the token as a Bearer header to any Sourdough Tracker endpoint your scopes allow. Pagination, filtering, and sorting are documented per model.
curl -H "Authorization: Bearer pat_…" \https://sourdoughtracker.com/xapi2/data/log_entry - 3
Subscribe to live updates
Open a single WebSocket and receive every create / update / delete event in real time - same access rules, same token. Skip polling entirely.
const ws = new WebSocket(`wss://${location.host}/xapi2/ch?token=${token}`)ws.onopen = () => ws.send(JSON.stringify({ op: "subscribe", id: "s1", dataType: "log_entry" }),)ws.onmessage = (e) => console.log(JSON.parse(e.data))
Navigate
These docs cover every endpoint the app exposes. Each model page carries concrete code samples in curl, JavaScript, TypeScript, and WebSocket.
JWT vs PAT, Bearer header.
Live events + CRUD over one socket.
Uniform error responses.
Per IP and per token.
2 data models available.
Native client for every endpoint - one line to install.
Plug Claude, Cursor & friends into your data.
Drop-in API wrappers for Python, TypeScript, Go, Java, Rust.
React to data changes in real time.
Data models
Production-grade, industry-standard data models. Every object is managed securely - validation, access rules, and audit run uniformly on every path - and the data is owned by the respective customer at all times. Export and deletion are first-class.
Arrows point from the referencing data model to the referenced one. Endpoint markers describe cardinality (e.g. * = any number, 1 = exactly one, 0..1 = optional). Click a node to open its model page.
log_entryOne row in the parent starter's continuous journal. Discriminated by kind ∈ {feed, bake, observation, milestone, photo}. Carries occurred_at, optional rise/aroma/bubble ratings, recipe details for bakes, an inline image via photo_blob_id, and a free-form body. The chronological feed on the starter detail page reads from this slice filtered by parent_id.
sourdoughA single sourdough starter. Carries identity (name, source, started_at), recipe defaults (flour_type, hydration_pct), state (last_fed_at, retired) and presentation (color, avatar_blob_id, tags, favorite). Acts as the parent for every log_entry in the starter's continuous journal.