API changelog: 2026
Every change to the Kintsugi API in 2026, newest first. For the latest changes and every release, see the API changelog.
2026-11-13
Breaking changesFilters exemptions by date range with startDate and endDateExemptionsBreaking change
On GET /exemptions and GET /v1/exemptions, the date filters are now range bounds, where they used to match one exact date. startDate (start_date on v1) returns exemptions whose validity start date is on or after that date. endDate (end_date on v1) returns exemptions whose validity end date is on or before that date. Setting endDate leaves out open-ended exemptions, the ones with a null end date. Sending both gives the exemptions that start and end inside the range. A request that sent the same date in both filters to find exemptions starting or ending on that day now returns every exemption inside the range instead.
- Review calls that send
startDateorendDate(start_dateorend_dateonv1) and expect an exact-date match. - To find exemptions that end on one day, filter with
endDateand discard rows whose end date is earlier. - Do not send
endDatewhen you want open-ended exemptions in the results.
2026-10-14
Breaking changesRejects null on exemption dates and status, and clears fein and salesTaxId on nullExemptionsBreaking change
PATCH /exemptions/{exemption_id} now answers 422 when startDate, reseller or status is sent as null; before, it answered 200 and changed nothing. null on fein or salesTaxId now clears the stored value, which then reads back as an empty string; before, it was ignored. endDate: null still removes the expiry. A field you leave out keeps its value. This applies to every Api-Version.
- Leave out
startDate,resellerandstatuswhen they should not change. - Send
nullforfeinorsalesTaxIdonly when you want the stored value removed.