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-10-19
Breaking changesCorrects null and empty values on five 2026-10-06 responsesBillingBreaking change
On Api-Version: 2026-10-06, a missing value is null for codes and identifiers and an empty string for free text. GET /billing/invoices/{invoice_id}/usage returns null for state, countryCode and requestType on a usage line that has none, instead of an empty string. A VAT report from GET /reports/jobs/{report_job_id}/result returns filingEntityRegistrationNumber: null when the filing has no registration number, instead of an empty string. PATCH /bank-details and POST /bank-details/{bank_details_id}/set-primary return an empty string for an unset bankName or accountHolderName, instead of null, as GET /bank-details already does. GET /connections/openmeter/{conn_id} returns storeName: "" when the connection has no label, instead of null. 2026-07-21 is unchanged.
- On
2026-10-06, treatstate,countryCode,requestTypeandfilingEntityRegistrationNumberas nullable, and test fornullinstead of an empty string. - Treat an empty
bankName,accountHolderNameorstoreNameas not set, and stop testing those fornull.
2026-10-07
Breaking changesLimits billing changes to an organization's Owners, Admins and own API keyBillingBreaking change
POST /billing/checkout, POST /billing/portal-session, PATCH /billing/plan and PATCH /billing now accept only the organization's own Owners and Admins and the organization's own API key. Any other caller that can reach the organization, including a Member, a partner user and a portfolio or reseller key, answers 403 with code forbidden; these callers were accepted before. A user acting through a portfolio is refused the same way. An organization you cannot access still answers 404, and the billing read endpoints are unchanged.
- Start checkouts, portal sessions and plan changes from the organization's own Owner or Admin session, or with its organization API key.
- Handle
403with codeforbiddenfrom these four endpoints.