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-11-19

Reports INPUT_VAT in the capabilities on GET /billing/details
NewBilling

GET /billing/details includes INPUT_VAT among the capabilities, with the same access values (INCLUDED, NOT_INCLUDED or REQUIRES_PAID_PLAN) as the other capabilities.

What to do
  • Read the INPUT_VAT entry to learn whether the organization may use input VAT. Ignore it if your integration does not gate on it.

2026-11-16

Adds paymentSource to GET /billing for non-card payment methods
NewBilling

GET /billing now returns paymentSource when the primary payment method is not a card, such as a bank account. It carries type (for example bank_account), status (for example valid or pending_verification), last4 and bankName, which is present only for a bank account. status, last4 and bankName are null when not reported. When the primary payment method is a card, card describes it and paymentSource is null. paymentSource is also null when no payment method is set or the billing system could not report it.

What to do
  • Read paymentSource when card is null to show a bank account or other payment method.
  • Accept paymentSource in strict response models of GET /billing.

2026-10-30

Returns entityType on invoice line items
NewBilling

Each line item on GET /billing/invoices now includes entityType, the kind of item the line bills: plan_item_price, addon_item_price, charge_item_price or adhoc (a one-time charge with no catalog item). It is always present. New values may be added, so handle an unknown value as a generic charge.

What to do
  • Use entityType to tell plan, add-on and one-time lines apart instead of matching on entityId or description.

2026-10-29

Accepts STARTER on POST /billing/checkout for every organization
Behavior changeBilling

POST /billing/checkout with billingPlan STARTER returns a hosted checkout URL for every organization, where it answered 400 for an organization that could not buy the current Starter plan yet. That organization is subscribed to the legacy Starter plan, so its billingPlan can read GROWTH after checkout. An organization that can buy the current Starter plan gets it, as before.

What to do
  • Read billingPlan from GET /billing after checkout instead of assuming the plan you requested, and treat GROWTH and STARTER as the Starter plan.

2026-10-23

Lists, adds and updates bank accounts by id
NewBilling

An organization can hold one bank account per country. GET /bank-details lists every account with the numbers masked to accountNumberLast4 and routingNumberLast4, the debit account first and marked by isPrimary; an organization with no accounts gets an empty list. POST /bank-details adds an account, requires country and answers 201. The first account becomes the debit account and a later one does not replace it. PATCH /bank-details/{bank_details_id} updates one account: an omitted field keeps its stored value, null clears any field except country, an empty body changes nothing, and an unknown id answers 404. A second account for a country already on file answers 409, and a country the API does not accept answers 422. Neither write changes the debit account; POST /bank-details/{bank_details_id}/set-primary does. An Owner or Admin user credential or an API key can call these routes, and a Member answers 403. On 2026-07-21, bankName and accountHolderName are null when not captured; on 2026-10-06 they are empty strings.

What to do
  • Call GET /bank-details to read every account, and use isPrimary to find the debit account.
  • Add an account with POST /bank-details and change one with PATCH /bank-details/{bank_details_id}, handling 409 for a country that already has an account.
Reports the Starter and Scale billing plans
Behavior changeBilling

billingPlan on GET /billing and GET /billing/details can now be STARTER or SCALE, in addition to FREE, GROWTH and PREMIUM. GROWTH and STARTER are both the Starter plan: GROWTH is a legacy subscription and STARTER is a current one.

What to do
  • Treat GROWTH and STARTER as the same plan, and accept SCALE wherever you read billingPlan.
  • Tolerate plan values you do not recognize.
Adds flatPrice to the billing estimate
NewBilling

GET /billing/estimate now returns flatPrice, true when the organization is billed a flat monthly price (the Scale or Premium plan) and false when it is billed per filing or registration. When it is true, unitCost is the flat monthly price and estimatedAmount equals it. premium stays true only for the Premium plan.

What to do
  • Read flatPrice, not premium, to tell whether the estimate is a flat monthly price.

2026-10-22

Records whether a bank account belongs to an individual or a business
NewBilling

Bank details now carry accountHolderType, INDIVIDUAL or BUSINESS. PATCH /bank-details accepts it, and sending null clears it; an omitted field keeps its stored value, and any other value answers 422. Responses from PATCH /bank-details and POST /bank-details/{bank_details_id}/set-primary always include accountHolderType, and it is null for an account where it was never recorded.

What to do
  • Send accountHolderType with PATCH /bank-details when you collect whether the account is held by an individual or a business, and handle null when you read it.
Returns the open checkout again when a checkout call repeats
Behavior changeBilling

POST /billing/checkout now returns the checkout the organization just started when you call it again for the same plan and price, for example after the user closes the hosted page. Before, the repeat call answered 409. A call that cannot reuse the open checkout, such as one still waiting on a completed payment, still answers 409.

What to do
  • Let a user reopen checkout by calling POST /billing/checkout again, and keep handling 409 for a checkout that cannot be reused.

2026-10-19

Breaking changes
Corrects null and empty values on five 2026-10-06 responsesBreaking change
Breaking changeBilling

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.

What to do
  • On 2026-10-06, treat state, countryCode, requestType and filingEntityRegistrationNumber as nullable, and test for null instead of an empty string.
  • Treat an empty bankName, accountHolderName or storeName as not set, and stop testing those for null.

2026-10-07

Breaking changes
Limits billing changes to an organization's Owners, Admins and own API keyBreaking change
Breaking changeBilling

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.

What to do
  • Start checkouts, portal sessions and plan changes from the organization's own Owner or Admin session, or with its organization API key.
  • Handle 403 with code forbidden from these four endpoints.
Reports access to each capability on billing details
NewBilling

GET /billing/details now fills in capabilities: one { capability, access } entry per capability, where access is INCLUDED, NOT_INCLUDED (the organization is on a paid plan that does not include it) or REQUIRES_PAID_PLAN (it needs a paid plan first). capabilities is null when access does not depend on per-capability settings for the organization, so gate on effectiveEntitlement instead. New capabilities and access values can be added, so treat an unknown access as not included and ignore a capability you do not gate on.

What to do
  • Read capabilities to show or hide a feature, and fall back to effectiveEntitlement when it is null.
Kintsugi API Changelog: 2026