Move a brew day and its planned cellar stays
Sets a brew's planned brew day (or, once brewed, its brew day) to another date and moves the brew's planned cellar stays by the same number of days, like changing the date on the brew page. Use it for 'push the saison brew day to Saturday'. Stays that already started never move. If the moved stays would overlap other beers' stays, nothing changes and the result has clash with would_push: show it, then call again with push: true to move those later too. date null clears the date (stays keep their dates). Dates YYYY-MM-DD. Brewed on another day than planned (set_brew_status says so)? Send align_to_brew_day: true instead of date: the planned stays move so the first one starts on the actual brew day, like the brew page's 'move the cellar plan' prompt (also works when that day is today). Needs the plan feature `cellar`. Scope: `brews:write` (or `write`).
Sets a brew's planned brew day (or, once brewed, its brew day) to another date and moves the brew's planned cellar stays by the same number of days, like changing the date on the brew page. Use it for 'push the saison brew day to Saturday'. Stays that already started never move. If the moved stays would overlap other beers' stays, nothing changes and the result has clash with would_push: show it, then call again with push: true to move those later too. date null clears the date (stays keep their dates). Dates YYYY-MM-DD. Brewed on another day than planned (set_brew_status says so)? Send align_to_brew_day: true instead of date: the planned stays move so the first one starts on the actual brew day, like the brew page's 'move the cellar plan' prompt (also works when that day is today).
Needs the plan feature cellar. Scope: brews:write (or write).
API token in format: bfk_. Each operation lists the token scope it requires (the scopes are listed below).
read: Read everything (all areas)write: Create, change and delete everything (all areas)brews:read: List and view brewsbrews:write: Create, update, delete brews and notesinventory:read: List inventory itemsinventory:write: Create, update, delete inventory itemsequipment:read: List equipment profilesequipment:write: Create, update, delete equipment profilesstyles:read: List style profilesstyles:write: Create, update, delete style profilesprofiles:read: List mash, fermentation, and water profilescustom-fields:read: List custom field definitionscustom-fields:write: Create, update, delete custom field definitionsprofiles:write: Create, update, delete mash, fermentation, and water profilescellar:read: View cellar, packaged stock, tap lists, and labelscellar:write: Manage cellar, packaging, stock, tap lists, and labelssettings:read: View preferences, imports, calculators, and your data exportsettings:write: Change preferences and undo importscommunity:read: View community, feedback, tickets, inbox, and account overviewcommunity:write: Post, vote, and reply in community, feedback, and tickets
In: header
Scope: brews:write
Request Body
application/json
The brew: its id, its batch number (e.g. 12 or "#12") or its exact name (e.g. "Citra Pale Ale"). Case does not matter.
New day, YYYY-MM-DD, e.g. "2026-11-21"; null clears it. Not with align_to_brew_day.
true = keep the dates and move the brew's planned stays so the first starts on its actual brew day (after brewing on another day than planned).
Which date to set: planned_brew_day (not brewed yet) or brew_day (the actual day). Default: brew_day if the brew has one, else planned_brew_day.
"planned_brew_day" | "brew_day"true = when the moved stays overlap others, move those later too (see clash.would_push of the previous call).
The brewer's local date today, YYYY-MM-DD (e.g. "2026-11-11"). Optional: defaults to today in UTC. Pass it when the brewer's day differs from UTC (late evening in America, early morning in Asia).
^\d{4}-\d{2}-\d{2}$Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://brewforge.sh/api/v1/actions/move_brew_day" \ -H "Content-Type: application/json" \ -d '{ "brew": "string" }'{
"moved": true,
"brew": {
"id": "string",
"name": "string"
},
"which": "string",
"from": "string",
"to": "string",
"stays_moved": 0,
"stays_kept": 0,
"pushed": [
{
"stay_id": "string",
"beer": "string",
"vessel": "string",
"by_days": 0,
"new_start_date": "string",
"new_end_date": "string"
}
],
"clash": {
"message": "string",
"overlaps": [
"string"
],
"would_push": [
{
"stay_id": "string",
"beer": "string",
"vessel": "string",
"by_days": 0,
"new_start_date": "string",
"new_end_date": "string"
}
],
"blocker": "string"
}
}{
"error": {
"code": "string",
"message": "string",
"hint": "string",
"candidates": [
{
"id": "string",
"name": "string"
}
],
"fields": {
"property1": [
"string"
],
"property2": [
"string"
]
},
"details": {}
}
}{
"error": {
"code": "string",
"message": "string",
"hint": "string",
"candidates": [
{
"id": "string",
"name": "string"
}
],
"fields": {
"property1": [
"string"
],
"property2": [
"string"
]
},
"details": {}
}
}{
"error": {
"code": "string",
"message": "string",
"hint": "string",
"candidates": [
{
"id": "string",
"name": "string"
}
],
"fields": {
"property1": [
"string"
],
"property2": [
"string"
]
},
"details": {}
}
}{
"error": {
"code": "string",
"message": "string",
"hint": "string",
"candidates": [
{
"id": "string",
"name": "string"
}
],
"fields": {
"property1": [
"string"
],
"property2": [
"string"
]
},
"details": {}
}
}{
"error": {
"code": "string",
"message": "string",
"hint": "string",
"candidates": [
{
"id": "string",
"name": "string"
}
],
"fields": {
"property1": [
"string"
],
"property2": [
"string"
]
},
"details": {}
}
}{
"error": {
"code": "string",
"message": "string",
"hint": "string",
"candidates": [
{
"id": "string",
"name": "string"
}
],
"fields": {
"property1": [
"string"
],
"property2": [
"string"
]
},
"details": {}
}
}