KintsugiKintsugi
API reference / Changelog / 2026

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-29

Breaking changes
Validates US routing and account numbers on bank account writesBreaking change
Breaking changeOrganizations

POST /bank-details, PATCH /bank-details/{bank_details_id} and PATCH /bank-details now check a US routing number or account number you add or change. A routing number must be 9 digits with a valid checksum, and an account number 4 to 17 digits. Spaces and dashes are removed before the check, and the digits are stored. A value that fails answers 422 with the field named in errors; it was stored as sent before. A number identical to the one already stored is not checked again, so saving other fields does not fail on an older value.

What to do
  • Send a routing number of 9 digits that passes the ABA checksum, and an account number of 4 to 17 digits.
  • Handle a 422 from these endpoints by showing the message for the field named in errors.

2026-10-28

Breaking changes
Sets the debit account with isPrimary on PATCH /bank-details/{bank_details_id}Breaking change
Breaking changeOrganizations

POST /bank-details/{bank_details_id}/set-primary is removed on every Tenanted release, including integrations pinned to 2026-07-21 or 2026-10-06. Send isPrimary: true on PATCH /bank-details/{bank_details_id} to make that account the organization's debit account, alone or together with field updates. false or omitted leaves the debit account unchanged. Unlike set-primary, this request accepts an API key as well as an Owner or Admin user credential. It still answers 404 when the organization has no account with that id. makePrimary on PATCH /bank-details is unchanged.

What to do
  • Stop calling POST /bank-details/{bank_details_id}/set-primary.
  • Call PATCH /bank-details/{bank_details_id} with isPrimary: true to change which account is the debit account.
Validates a US ein on PATCH /organization-detailsBreaking change
Breaking changeOrganizations

When the organization is incorporated in the US, ein on PATCH /organization-details must be 9 digits, with or without the dash (XX-XXXXXXX). The value is stored with the dash. A value that is malformed, starts with 9 or is all zeros answers 400; it was stored as sent before. An ein identical to the stored value is not checked again, so saving unrelated fields does not fail on an older value. Changing the incorporation country to the US checks the stored value. Outside the US, ein stays a free-form business ID. Blank ein on a US organization is ignored, and null for taxId removes the tax id as before.

What to do
  • Send a US ein as nine digits or XX-XXXXXXX, and never one that starts with 9 or is all zeros.
  • Handle a 400 from PATCH /organization-details by asking the user to correct the number.

2026-10-15

Breaking changes
Limits how fast an organization can send invitationsBreaking change
Breaking changeOrganizations

POST /users/invites now counts against a limit per organization, which it shares with the legacy invite endpoint. A request over the limit answers 429 with the error code rate_limited and a Retry-After header that gives the seconds to wait. Before, there was no limit. Every request that passes validation counts, including one that repeats an existing invitation or is refused for its role. This applies to every Api-Version.

What to do
  • Wait the number of seconds in Retry-After before retrying a 429.
  • Space out bulk invitations, and do not retry a refused invitation in a loop.

2026-10-14

Breaking changes
Rejects null on organization settings, exemption reminder settings and user role updatesBreaking change
Breaking changeOrganizations

PATCH /organization-settings and PATCH /organization-settings/exemption-reminders now answer 422 when any field is sent as null; before, they answered 200 and changed nothing. PATCH /users/{user_id} answers 422 when additionalRoles is null; before, null was treated as omitted and kept the member's additional roles. A field you leave out is unchanged, false is written as sent, and additionalRoles: [] still clears the additional roles. This applies to every Api-Version.

What to do
  • Leave out a setting you do not want to change instead of sending null.
  • Send additionalRoles: [] to remove a member's additional roles, and leave the field out to keep them.
Answers 200 with the stored record to an empty bank details updateBreaking change
Breaking changeOrganizations

PATCH /bank-details with an empty body now changes nothing and answers 200 with the stored record, or null when none exists. Before, it answered 400. It does not create a record. A client that reads the response must handle null. This applies to every Api-Version.

What to do
  • Handle a null response body, and do not rely on 400 to detect an update with no fields.

2026-10-09

Breaking changes
Updates organization details one field at a timeBreaking change
Breaking changeOrganizations

PATCH /organization-details now changes only the fields you send. Before, a section you sent replaced the whole section, so its identity fields were required and an omitted optional such as address2 was cleared. Now an omitted section or field is left unchanged, and a sent field is written as sent, including an empty string, 0 and false. null clears a field whose description says it accepts null, which now includes taxId, homeStateRegistration, naics, businessPhone, businessEmail and businessFiscalYearEnd, so a null that was ignored before now removes the stored value. null on any other field answers 422. Sending taxId needs an incorporation country, sent in the same request or already stored, or the request answers 400. This applies to every Api-Version.

What to do
  • Send only the fields you want to change. To keep a value, leave the field out.
  • Stop sending null to mean "leave unchanged": it now clears the field, or answers 422 where the field cannot be cleared.
  • Set the incorporation country before, or with, taxId.
Kintsugi API Changelog: 2026