Changed
-
The inventory checks every request against the published API description. This is about
your own API clients; the app sends nothing that is refused now (it sends location ids as
numbers from this release on, also in the order of locations and child locations). Under
/api/v1/inventory, input that used to be quietly accepted, reinterpreted or answered later
is now refused with a 400:- everywhere: a path id that is not plain digits, such as
12abc,5.0,1e2or0x10
(DELETE /inventory/items/12abcdeleted item 12), a number, truth value, list or object in
a text field (it was stored as text), and a number written as text, a truth value or a
list in a number field ("12.5",trueand[5]were read as numbers); - items: a
condition,statusorodometer_unitoutside its list, andfalseor0for
them (they meant the default; null,""or leaving it out still do), a day that is not
YYYY-MM-DDor is a list, a location id that is neither a whole number nor digit text,
warranty_monthsoutside 0 to 600, an odometer reading that is not a whole number - also
for a category without one, where it was dropped silently - and a price that is not a
number, also from an account without the price right (it was ignored); tracked_datesandattachment_document_idsthat are not a list: on a replace, null,
text or an object REMOVED all tracked dates with their reminders, or all document links.
Leaving the field out still leaves them as they are, and[]still clears them. Tracked
date rows that are not objects, without label or day, or with numbers outside their range;- linking a booking:
entry_idas text or left out, aroleoutside its list,
amount_shareas text or below zero; completing a tracked date and the service log: a day
that is notYYYY-MM-DD, an odometer reading as text or below zero; - the list:
statusoutside its list,location_idthat is not plain digits, and a filter
given twice (they were ignored or read as the first); - the order of locations, child locations and categories with entries that are not ids or
keys ([{}]and[true]were a 500, other entries were skipped or stored), and an order
of child locations withoutorder(it was a silent no-op;[]still is).
What stays allowed is in the description now too: null or
""for "no value" where the
routes read it so, digit text for a location id (older app versions send it), a currency in
any case, unknown fields. APUTreplaces the whole item, as before: left-out fields are
cleared or take their default, only the name is required, andtracked_datesand
attachment_document_idsstay untouched when left out. Rules the description cannot carry
stay with the routes and their sentences: an empty name after trimming, a day that does not
exist, a category or location that does not exist (inventory_selected_location_not_found
as before, for a number and for digit text), the photo content, the odometer that must not
fall below the current reading. The check runs before the entry is looked up, so a bad
request for a missing entry is a 400, not a 404 or 409, and an account that may change only
its own items gets 400 for a bad request on someone else's item and, as before, 403
not_ownerfor a valid one. Text lengths count the value as sent. - everywhere: a path id that is not plain digits, such as
-
Housekeeping and rewards check every request against the published API description.
This is about your own API clients; the app sends nothing that is refused now (it sends the
housekeeper id as a number from this release on). Under/api/v1/housekeepingand
/api/v1/rewards, input that used to be quietly accepted, reinterpreted or answered later
is now refused with a 400:- everywhere: a path id that is not plain digits, such as
12abc,1.9,0x10or1
(they were read as numbers), a number, truth value, list or object in a text field (it was
stored as text), and a number written as text, a truth value or a list in a number field
("60",trueand[5]were read as numbers) - for amounts also from an account without
the amounts right, where they were ignored; PUT /rewards/participants/{userId}withoutenabled, or with anything buttrueor
false("true",1,null): it SWITCHED THE PARTICIPATION OFF.enabledis required
now.PATCH /rewards/catalog/{id}withis_activethat is nottrueorfalse: it
switched the reward off;- lists:
payment_scheduleandrate_typeof a housekeeper,actionof a redemption
decision (missing or unknown, it was 400 only after the request was looked up),kindof a
request,frequencyof a pocket money plan anddirectionof a money entry outside their
values;birth_year_unknownas0,1or null; - ids in a body (housekeeper, receipt, person, reward) that are neither whole numbers nor
digit text, andnullfor a person or reward in rewards; whole numbers outside the
route's own bounds (a reward's cost and quantity, a bonus, a plan's anchor day, a task
frequency below 1); - queries:
?month=outside 01 to 12 or before the year 1001 (2026-13was a 500),
worker_id,user_id,limitandtimezone_offset_minutesthat are not plain digits
(?user_id=abclisted everybody),local_datethat is notYYYY-MM-DD,status,kind
andalloutside their values, and any filter given twice.
What stays allowed is in the description now too: null or
""for "no value" where the
routes read it so, digit text for ids (the legacy form), unknown fields, a body on the routes
that read none. Rules the description cannot carry stay with the routes and their sentences:
an empty name after trimming, the username rule (housekeeping_username_invalid), a day that
does not exist, amounts below zero, the money amount and currency of an account. Texts the
rewards routes cut (icon,note,reason) are still cut, not refused. The check runs
before the entry 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 ofPOST /housekeeping/workerand of the rewards
admin routes, and the shopping right ofPOST /housekeeping/supply-requests, come first:
403 stays 403, also for a bad request. Text lengths count the value as sent. - everywhere: a path id that is not plain digits, such as
-
Waste collection and the shift schedule 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/wasteand/api/v1/schedule, input that used to be quietly accepted,
reinterpreted or answered later is now refused with a 400:- everywhere: a path id that is not plain digits, such as
12abc,1.5or1e3(they were
read as 12, 1 and 1), a number, truth value, list or object in a text field, and a number
written as text, a truth value or a list in a number field ("7"for a cycle length,""
orfalseforreminderOffsetMinutes, which meant 0 minutes); PUT /waste/reminder-settings/{typeId}withoutenabled,offset_daysand
delivery_time: a body withoutenabledSWITCHED THE REMINDER OFF, and a missing lead
time or time was reset to 1 day and 08:00. All three are required now;- switches that are not
trueorfalse(active,archived,ignored,enabled,
is_active,overtimeEnabled):active: "false"kept a waste schedule running; - garbage that was a 500:
type_id: trueor{}for a waste schedule or pickup, anote
that is not text on a moved or skipped pickup,mappings: [null]on an import commit, and
color: ""for a waste type; - lists: a
recurrence_kindor weekday code outside its values, weekdays as comma text
("MO,TH"; send a list), a mapping profileversion
other than 1,include_archivedandinclude_inactiveother than1,true,0or
false; - ids in a body that are neither whole numbers nor digit text (
user_id,shift_type_id,
custom_field_id, the type of a schedule or pickup); bounds the routes have on every
value (cycle length 1-366, at most 500 cycle days, reminder minutes 0-1440, weekly hours
1-168, waste reminder lead time 0-14 days); - queries:
type_id,user_id,fromandtothat are not plain digits orYYYY-MM-DD
(?type_id=abclisted every schedule,?user_id=3abcread 3), and any filter given twice; - missing fields that were answered later:
profile_digestof a mapping profile commit and
expected_versionof a re-import commit (a 409 before), and a day in the path of a waste
override that is notYYYY-MM-DD(a 404 before).
What stays allowed is in the description now too: null or
""for "no value" where the
routes read it so, digit text for ids (the legacy form), weekdays as a list or one code,
unknown fields, an empty body where every field is optional (skipping a pickup
date), a URL source withoutics. Rules the description cannot carry stay with the routes
and their reasons: an empty name after trimming, a day that does not exist, the anchor day of
a schedule, the interval bound per kind, a type, shift type or member that does not exist,
the refresh interval of a URL source (with its bounds asparams). The check runs before the
entry is looked up, so a bad request is a 400, not a 404, 403 or 409; a valid one meets those
as before. A member who names someone else inuser_idof a pattern, override, extra shift
or their range variants gets 403 first, also for a bad request, now with the plain sentence
Forbidden.. Text lengths count the value as sent. - everywhere: a path id that is not plain digits, such as
-
A path id beyond the safe integer range is refused with a 400. This is about your own
API clients; the app never sends such an id. On the routes that check requests against the
API description (notes, birthdays, quick links, reminders, notification channels,
permissions, displays, profile pictures, recipes, recipe providers, pantry, inventory,
housekeeping, rewards, waste collection, shift schedule), a
path id above 9007199254740991 is now a 400 with the rulemaximum, and a run of digits too
long to be a number at all (hundreds of digits) a 400 with the ruletype. Before, such an id
answered 404 or 400 depending on the route. 9007199254740991 itself,0and a negative id
are answered by the route as before. The API description gives every numeric path id this
upper bound.