Changed
-
The budget and the subscriptions check every request against the published API
description. This is about your own API clients; the app sends nothing that is refused now.
Under/api/v1/budget(accounts, categories, entries, series, loans, plans, statistics,
transfers) and/api/v1/budget/subscriptions, input that used to be quietly accepted,
replaced or answered with a 500 is now refused with a 400:- a path id that is not plain digits:
1abc,1.0and1e0reached account, entry or loan 1,
0x1and1.0reached transfer or subscription 1 - also to delete it, andPOST /subscriptions/0x1/renewbooked a payment; - a month outside 01 to 12:
GET /budget?month=2026-13with a running series wrote an entry
dated2026-13-05, a loan storedstart_month: "2026-13", and the summary, the plan and
the export answered for month 13; a day that is notYYYY-MM-DD(anchor=2026-13-45of the
statistics answered 500); - a number, list, object or truth value in a text field: an account, category, entry,
transfer, loan or subscription category named{}was stored as"[object Object]", a
number as text; on editing an entry, a series, a loan or a subscription a number answered
500; null, an empty string, text, a truth value or a list as an amount:nulland""set an
entry, a series, an account's starting balance or the subscription budget to 0,true
counted as 1,[5]as 5,"0x10"as 16;credit_limit: ""is nownullto clear it;- an unknown
interest_modeof a new loan became a loan without interest, an unknown
visibilityof an entry, transfer, loan or subscription the default; an unknown loan
directionor accounttype(""was stored as the type), categorytype,
recurrence_interval(nullanswered 500),billing_cycle(missing or""answered
500) orend_type; - switches that are not
true/false(0/1on entries):is_recurring: "false"started
a series,archived: "false"archived an account; - ids in a body that are not whole numbers:
account_id: ""or"1", a subscription's
category_id: true(a 500),responsible_user_idsandattachment_document_idswith
non-numbers (dropped silently), the order lists (order: [{}]of the categories answered
500, missing or empty changed nothing; the subscription order took any list); - a
queryof the logo search that is not text (5was looked up as the website5); - a query value outside its type, or given twice:
scope=x,account_id=abc,loan_id=abc,
a month of the export or plan that is notYYYY-MM(the current month),range=day,
include_archived=yes, a subscriptionstatus,enabled,category_idor
payment_method_idoutside its values (no filter, or an empty list).
The check runs before the row is looked up, so a bad request is a 400, not a 404 or 403 (the
write rule of the personal budget mode); a valid one meets those as before. Lengths, ranges,
the calendar day and every refusal with areasonthe budget page shows stay with the routes;
a body of the wrong type now answersreason: validationwith the field (for example
entry_date_invalidfordate: "nope",loan_direction_invalidfor an unknown direction).
The loan preview answers an unknowninterest_modewith 400 instead of{ ok: false }. A
PUT without a body is a 400;PATCH /budget/{id}/confirmstill takes none. An unexpected
error of a subscription route now answersInternal server error.like every other route
(it wasInternal error.). - a path id that is not plain digits:
-
The shopping list, documents, the document storage settings and the DMS connection check
every request against the published API description. This is about your own API clients;
the app sends nothing that is refused now (from this release on it sends the folder of a
document, the DMS account and the order of the shopping categories as numbers). Under
/api/v1/shoppingand/api/v1/documents(withstorage/google-driveanddms), input that
used to be quietly accepted, replaced or answered with a 500 is now refused with a 400:- a path id that is not plain digits:
0x1,1.0and1e0reached document 1, and on the
shopping list1.0reached list or item 1; - a number, list, object or truth value in a text field: a shopping list, shop, category,
folder or document named{}was stored as"[object Object]", a number as text; - an unknown
visibilityof a new or linked document becamefamily, visible to the whole
household; an unknowncategorybecameother, and on editing a document an unknown
visibility,categoryorstatuswas ignored; - an unknown DMS
providerbecamepaperless; adms_document_idthat is neither text nor a
number was stored as its text (true,"[object Object]"); - an unknown
folder_keyof an upload was dropped; an unknownselected_upload_backend, an
enabledof the WebDAV settings that is nottrueorfalse; - a number field sent as a truth value, text or list:
expiry_reminder_days: truewas stored
as 1,price_cents: true,[]and"0x10"as 1, 0 and 16; ids in a body that are not
whole numbers or digit text (folder_id,parent_id,subject_user_id,account_id,
document_id;parent_id: trueand"0x1"were read as folder 1); archived: "false"and0archived a document;preview: "true"of the meal-plan import
ran the real import;is_checkedother thantrue,false,0or1;orderof the shopping categories that is not a list of ids ([{}]and[true]answered
500,[1.5]and["x"]changed nothing),itemsof the pantry import that is not a list
of entries (taken as empty),idsof the kitchen undo that are not whole numbers (dropped);- a query value outside its type, or given twice: a doubled
qof the shopping suggestions
answered 500;status,category,folder_idandexpiringof the document list and an
emptydocumentsof a folder deletion fell back silently to no filter orunfile;
limitof the price history outside 1 to 50 was clamped.
The check runs before the row is looked up, so a bad request is a 400, not a 404, 403 or 409;
a valid one meets those as before. The admin check of the storage settings, Google Drive and
every DMS route, and the meal-plan and pantry rights of the two kitchen imports come first:
403 stays 403, also for a bad request. Lengths stay with the routes. Sharing a document with
an id that has no account answers the 400 of a non-member instead of 500. A DMS account stored
with a built-in property name as its provider no longer reaches a broken adapter. - a path id that is not plain digits:
-
Contacts, contact sync and the meal plan check every request against the published API
description. This is about your own API clients; the app sends nothing that is refused now
(from this release on the meal dialog sends the chosen recipe as a number). Under
/api/v1/contacts,/api/v1/contacts/cardavand/api/v1/meals, input that used to be
quietly accepted, replaced or answered with a 500 is now refused with a 400:- a path id that is not plain digits:
0x10andabcfound nothing (404),1e2reached row 1; - a number, list, object or truth value in a text field: a contact named
{}was stored as
"[object Object]", a number as text; on editing a contact or a meal, and on the
ingredients of a meal, a number answered 500; recipe_idandcook_user_idthat are neither whole numbers nor digit text ("0x10"was
read as recipe 16,trueas 1 or a 500), alistIdof a transfer that is not a whole
number, a meal type that is empty ornull, a series end that is not a day;ingredientsandassignmentsthat are not lists of objects (500);- an unknown
scopeonPUTandDELETE /meals/{id}: onDELETEit deleted the meal; weekof the meal plan that is not a day:abcand an empty value fell back to the current
week,2026-13-45answered 500,2026-02-30rolled over into March;orderof the contact categories that is not a list of text (taken as empty, or 500 for an
object entry), a category edit with neithernamenorcolor;- CardDAV: account fields that are not text (a password that was not text counted as empty),
enabledof an address book that is nottrueorfalse; the refusal carries
reason: "validation"and noerrorCode, and the contact sync page says its sentence for
it; - queries given twice (a doubled
qof the meal suggestions answered 500).
The check runs before the row is looked up, so a bad request is a 400, not a 404, 403 or 409;
a valid one meets those as before. The admin check of contact sync and the shopping write
right of the two transfers to the shopping list come first: 403 stays 403, also for a bad
request. Lengths stay with the routes, with theirreasonandparams.limit. Deleting a
contact sync account that does not exist answers 404 (account_not_found) instead of 500. A
week start stored as a built-in property name (constructor) no longer breaks the meal plan. - a path id that is not plain digits:
-
The shops and the price history of the shopping list answer an unexpected failure with the
same sentence as the rest of the API.GET,POST,PUTandDELETEunder
/api/v1/shopping/storesandGET /api/v1/shopping/price-historysaid"Internal error"on
a server-side failure; they now say"Internal server error."like every other module. Status
500 andcodeare unchanged, and so is every answer that names a known cause. -
Health answers an unexpected failure with the same sentence as the rest of the API.
Vitals, medications and the dose log, lab reports, activities, the CSV exports, the cycle
tab, caregivers, preventive care and nutrition under/api/v1/healthsaid
"Internal error."on a server-side failure; they now say"Internal server error."like
every other module. Status 500 andcodeare unchanged. Every answer that names a known
cause stays as it was: the fasting refusals with theirreason(and thecurrentrecord of
a conflict), an undo of a dose that is not recorded (health_dose_pending), the reasons of
the cycle import, the vital limits and units, and the refusals of care. The cycle feed,
fasting and the visibility defaults answered this way already. -
Health checks every request against the published API description. This is about your
own API clients; the app sends nothing that is refused now (from this release on it sends the
type of a preventive-care record as a number). Under/api/v1/health, input that used to be
quietly accepted, replaced or answered later is now refused with a 400:- a path id that is not plain digits:
7abc,1e2,1.5and" 5"reached row 7, 1, 1 and
5, and on fasting records0x10reached record 16; - a number sent as text, a truth value or a list in a number field:
"0x10"," ",[]and
truewere stored as 16, 0, 0 and 1 (vital values, stock and doses, lab values, activity
numbers, nutrients, cycle settings); - an unknown value where the module has a list: visibility, dose status, lab flag, cycle flow
and the day log choices, basal temperature unit, contraception, preventive-care kind, meal
type, the areas of the visibility defaults;activeandprnof a new medication or
schedule that are nottrue/false/1/0became the default; - a number, list or object in a text field (stored as text,
{}as"[object Object]"), ids
in a body that are neither whole numbers nor digit text (user_id,schedule_id,
type_id,notify_partner_user_id),symptomsthat is neither a list nor text (it cleared
the day's symptoms) andresultsof a lab report that is not a list (dropped); caregiver_idswith an entry that is not an id:["abc"]WITHDREW ALL CARE for the person;PATCH /health/fasting/{id}withvisibility: null, which made a shared fast private;
fastinggoal_minutes,ratingandexpected_revisionsent as text;- queries:
user_idthat is not plain digits or0(read as "everybody visible"),active
other than1,0,true,false, export dates that are not a day (ignored), an unknown
meal_type, and any parameter given twice; - a missing body on the routes that read one;
{}sent on purpose still passes where the
route took it before.POST /health/logs/{id}/skipreads no body.
The check runs before the row is looked up, so a bad request is a 400, not a 404 or 409; a
valid one meets those as before. The fasting capability and the admin check of caregivers and
preventive-care types come first: 403 stays 403, also for a bad request. Rules the
description cannot carry stay with the routes: vital limits and units, the order of start and
end, the CSV import rows, revisions and overlaps of fasts. A basal temperature unit named like
a built-in property (constructor) no longer passes the range check. - a path id that is not plain digits:
-
Editing a shared expense takes the whole expense. This is about your own API clients; the
app sends every field now.PUT /split-expenses/expenses/{id}withoutdescription,
currency,converted_amount,converted_currency,exchange_snapshot,split_methodor
expense_datecleared the stored note and exchange snapshot, read the amount in the converted
currency, set the converted amount and currency back to the amount and currency, split the
amount equally and moved the expense to today. All seven are required now besidestitleand
amount;nullstill clears the note and the snapshot and stands for the amount, and
expense_date: ""is still today.payer_id,participants,category,budget_category
andattachment_document_idsstay optional and keep the stored value when left out. The edit
dialog no longer drops the stored conversion and exchange snapshot of an expense whose amount
and currency it leaves unchanged, and the exact shares of such a converted expense are entered
and checked in the converted currency, as the server adds them up. -
Saving the cycle settings takes all of them. This is about your own API clients; the app
sends every field already.PUT /health/cycle/settingswithout one of its fields reset it to
its default: the cycle and period lengths, the due date, contraception, the period reminder
and the partner notification were cleared, the luteal phase went back to 14 days, fertility
tracking and the PMS window were switched on, pregnancy and perimenopause mode and the daily
log nudge were switched off and the default visibility becameprivate({}reset them all).
All 14 fields are required now;nullstill clears a value where the field takes it, and
luteal_length: nullis still 14. -
Saving a cycle day again takes the whole day. This is about your own API clients; the app
sends the whole day already.POST /health/cycle/logson a day that has a log withoutflow,
note,visibility,symptoms,basal_temp,basal_temp_unit,cervix_mucus,lh_test,
pregnancy_testorintimacycleared the stored value, emptied the symptoms and made the day
private. These ten are required now besideslog_date;nulland""still mean "not
given".feelingsandmoodstay optional and keep the stored feelings when both are left
out. -
Setting a nutrition target takes all eight nutrients. This is about your own API clients;
the app sends all eight already.PUT /health/nutrition/targetswithout a nutrient unset it,
and{}deleted the whole target. All eight are required now;nullunsets one, and eight
nullstill delete the target.user_idstays optional and means the caller when left out. -
Recording a dose takes its status. This is about your own API clients; the app sends it
already.POST /health/medications/{id}/logswithoutstatusstoredpending, and repeating
a planned dose that was taken (sameschedule_idandscheduled_at) reset it topending
and dropped its time.statusis required now;nullstill meanspending.taken_at,
dose_qty,noteandstock_deductstay optional: left out, a repeat keeps the stored time,
dose and note and deducts nothing. -
Renaming a contact takes all five name parts. This is about your own API clients.
PUT /contacts/{id}with some offirstName,lastName,middleName,namePrefixand
nameSuffixcleared the ones left out, so a middle name, title or suffix from a vCard or
CardDAV was lost. Sent together they are required together now: one without the others is a
400 naming a missing part;nullstill clears a part, and leaving out all five keeps them. -
Editing a document takes its access list. This is about your own API clients; the app
sends it already.PUT /documents/{id}withoutallowed_member_idsemptied the list, so a
restricteddocument silently lost every member it was shared with.allowed_member_idsis
required now ([]shares it with nobody); forfamilyandprivateit is ignored as before.
Every other field stays optional and keeps the stored value when left out. -
An exchange snapshot is an object or
null. This is about your own API clients: on
POST /split-expenses/groups/{id}/expensesandPUT /split-expenses/expenses/{id},
exchange_snapshotsent asfalse,0,""or any other value that is not an object is now
refused with a 400, wherefalse,0and""were stored as no snapshot and other values as
sent. -
Backup answers an unexpected failure with the same sentence as the rest of the API.
GET /api/v1/backup/databasesaid"Database backup failed.",POST /api/v1/backup/trigger
"Backup trigger failed."andPUT /api/v1/backup/webdav/config"Failed to save WebDAV config."on a server-side failure; they now say"Internal server error."like every other
module. Status 500 andcodeare unchanged. Every answer that names a known cause stays as it
was: a download whose backup failed its integrity check (backup_verify_failed), a local
failure of the WebDAV upload (backup_local_failed), the 502 of the WebDAV server, the
errorCodeof the WebDAV settings and the reasons of a restore. Shared expenses answered
this way already. -
Shared expenses, backup and the system diagnostics check every request against the
published API description. This is about your own API clients; the app sends nothing that
is refused now (from this release on it sends the payer and payee as numbers). Under
/api/v1/split-expenses,/api/v1/backup,/api/v1/systemand/api/v1/changelog, input
that used to be quietly accepted, replaced or answered later is now refused with a 400:- a path id that is not plain digits:
0x10,1e1and" 5"read group, expense or
recurring expense 16, 10 and 5, and7abcor1.5were a 404; - an unknown value where the module has a list: group
type,default_currency,
default_split_method, an expense or settlementcurrencyandconverted_currency,
split_method,category, a recurringfrequency, a memberrole, a guest
family_role, and the filtersstatus(groups) andcategory(expenses). They were
replaced with a default (general,equal, the group currency,guest,other) or
ignored; - a number, truth value, list or object in a text field (a guest
password: {}was stored as
"[object Object]"), an amount sent as a number, and ids in a body that are neither whole
numbers nor digit text (payer_id,payee_id,participants,splits[].user_id,
user_id,contact_id,proof_document_id,attachment_document_ids); attachment_document_idsthat is not a list onPUT /split-expenses/expenses/{id}:
null, a single id or text REMOVED EVERY RECEIPT of the expense. Leave the field out to
keep them, send[]to remove them;PUT /backup/webdav/configwith ausername,passwordorremotePaththat is not text
(username: 5was a 500) or akeepthat is not a whole number (7.5was stored as 7);- queries:
limit,offsetandbefore_idthat are not plain digits,recurringother than
1, and any parameter given twice.limitabove 100 and a negativeoffsetare still
capped, as described; - a missing body on the routes that read one;
{}sent on purpose still passes where the
route took it before (PATCH /split-expenses/groups/{id}).
What stays allowed is in the description now too:
nullor""for "no value" where the
routes read it so, digit text for ids (the legacy form), unknown fields, no body at the pause
toggle. Rules the description cannot carry stay with the routes and their sentences: an empty
name after trimming, amounts and their decimal places, the sums of a split, membership,
budget categories (unknown_budget_category), the WebDAV address pattern and password rule
(errorCode).missedkeeps its reasoninvalid_missed. The check runs before the group,
expense or recurring expense is looked up, so a bad request is a 400, not a 404, 403 or 409;
a valid one meets those as before. The admin check of backup and diagnostics and the refusal
of a shared-expense guest creating a group come first: 403 stays 403, also for a bad request.
Text lengths count the value as sent. - a path id that is not plain digits:
-
Replacing a moved or skipped waste pickup or a day of the shift schedule takes the whole
entry. This is about your own API clients; the app sends every field already. APUT
replaces what is stored, so a field left out no longer stands for a value:PUT /waste/schedules/{id}/overrides/{originalDate}withoutreplacement_dateandnote:
an empty body skipped the pickup, and a missing note wiped the stored one. Both are required
now;replacement_date: nullskips the pickup;PUT /schedule/overrides/{dateKey}withoutshift_type_id,noteandfield_values: a
missing shift type made the day free, a missing note wiped the stored one, and missing field
values kept the stored ones while everything else was replaced. All three are required now;
shift_type_id: nullis the free day, andfield_values: {}clears the values.user_id
stays optional and defaults to you.
-
Waste collection and the shift schedule answer an unexpected failure with the same sentence
as the rest of the API. The routes under/api/v1/waste(types, schedules and their
overrides, one-off pickups, occurrences, import sources, file import, reminder settings) said
"Internal error"on a server-side failure,DELETE /api/v1/schedule/shift-types/{id}said
"Internal error."andGET /api/v1/schedule/entriessaid"Schedule entries could not be resolved."; they now say"Internal server error."like every other module. Status 500 and
codeare unchanged. Every answer that names a known cause stays as it was: a refused input,
a missing record or a conflict of waste collection, the 502 of a subscribed address without
calendar entries, and the 409 of a shift type still in use. The waste feed, the schedule feed
and the own schedule settings answered this way already.
Fixed
- Saving a contact in the app keeps its middle name, title and suffix. A contact imported
from a vCard or synced over CardDAV lost them the first time its form was saved, because the
form sent only the first and last name; it now sends the stored ones along. - A shared expense converted into a currency with other decimal places reports the converted
amount correctly.converted_amountin the expense answers was written with the decimal
places ofcurrencyinstead ofconverted_currency: 1500 JPY converted from USD read
"15.00", and sending it back was refused.converted_amount_minorwas always right. - Exact shares of an expense converted into COP, HUF, IDR or IRR can be saved again. The
converted amount keeps two decimal places (for example 3581.47 HUF), but the share fields
allowed none for these currencies, so the shares could never add up to it. They now accept
the decimal places the converted amount is stored with. - The running total under exact shares of such an expense shows the stored decimal places.
It showed 3,581 HUF while the shares had to add up to 3,581.47 HUF; it now shows 3,581.47 HUF. - A shared expense saved without an exchange rate answers
exchange_snapshot: null. Creating
or replacing an expense without a rate stored the text"null", and the expense answers
returned"exchange_snapshot": "null"for it. New and replaced expenses now store no value and
answernull; expenses saved before keep"null"until they are saved again.