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

Returns state tax authority websites from the certificate catalog
NewExemptions

GET /public/exemption-requests/{token}/missing-certificates/certificate-catalog returns taxAuthorities, one entry per US state ordered by state code, each with jurisdiction and the https websiteUrl of that state's tax authority. It lists every state, including a state with no form in forms. The address is the authority's public website, not a filing or login portal.

What to do
  • Link websiteUrl where a purchaser needs the state's own guidance, including for a state with no downloadable form.

2026-11-16

Lists downloadable certificate forms with GET /public/exemption-requests/{token}/missing-certificates/certificate-catalog
NewExemptions

GET /public/exemption-requests/{token}/missing-certificates/certificate-catalog returns the blank exemption certificate forms a purchaser can download and fill in. The link token is the only credential. The response is forms, ordered by jurisdiction and then formName, with multi-jurisdiction forms last. Each form has jurisdiction (the US state code, or null for a form several states accept), formName, formNumber (null when the form has none) and templateFile, the path of the blank PDF relative to the tax-forms/ folder of the public downloads host, such as ca/cdtfa-230.pdf. A state with no accepted form does not appear. The endpoint answers 404 when the link is unknown, 410 when it is closed or expired, and 422 when the token is malformed.

What to do
  • Call the endpoint with the purchaser's link token to show which certificate forms apply, and build each download address from templateFile.

2026-11-13

Breaking changes
Filters exemptions by date range with startDate and endDateBreaking change
Breaking changeExemptions

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.

What to do
  • Review calls that send startDate or endDate (start_date or end_date on v1) and expect an exact-date match.
  • To find exemptions that end on one day, filter with endDate and discard rows whose end date is earlier.
  • Do not send endDate when you want open-ended exemptions in the results.

2026-11-10

Adds ZOHO_BOOKS as an exemption source
NewExemptions

Exemptions that come from a Zoho Books connection report ZOHO_BOOKS as their source. The value appears in the exemption source field and wherever a transaction returns the source of its exemption.

What to do
  • Accept ZOHO_BOOKS wherever your code switches on the exemption source, including strict enums in generated clients.

2026-10-29

Ends a deactivated exemption's date window on PATCH /exemptions/{exemption_id}
Behavior changeExemptions

Setting status to DEACTIVATED now closes the exemption's date window: an endDate that is empty or later than today (UTC) becomes today, or the startDate when that is later, so later sales are taxed and sales dated up to the end date keep their treatment. An earlier endDate is kept. While the exemption stays DEACTIVATED, an edit cannot push endDate past that day. Setting status back to ACTIVE without an endDate restores the end date the deactivation replaced, including no end date, unless you changed endDate after deactivating.

What to do
  • Read endDate from the response after deactivating, since it can differ from the value you sent.
  • Send an endDate with status ACTIVE when you reactivate an exemption and want a specific expiry.

2026-10-14

Breaking changes
Rejects null on exemption dates and status, and clears fein and salesTaxId on nullBreaking change
Breaking changeExemptions

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.

What to do
  • Leave out startDate, reseller and status when they should not change.
  • Send null for fein or salesTaxId only when you want the stored value removed.

2026-09-30

Adds partial exemptions for California partial exemption certificates
NewExemptions

A new exemption type, partial, records a customer's California partial exemption certificate, such as the one for qualifying manufacturing and research equipment. Unlike a full exemption, a sale to that customer stays taxable: Kintsugi applies the reduced rate the certificate allows to qualifying items sold in California. Create one with exemption_type partial and a certificate_type on POST /v1/exemptions, or with exemptionType and certificateType on POST /exemptions and POST /exemptions/bulk in the 2026-07-21 release. The certificate type is the form's code from GET /v1/exemptions/partial-certificate-types, which lists each form's code, name, jurisdiction and country; its optional jurisdiction parameter narrows the list to one state, ignoring case. Today the list holds nine California forms. A partial exemption needs country US and jurisdiction CA, and the certificate type is accepted only on a partial exemption. Exemptions, including those embedded in transactions, now report the certificate type, which is null for every other type. Partial exemptions are available to organizations that have them enabled; for any other organization, creating one answers 400.

What to do
  • Send exemption_type: "partial", a certificate_type from the forms list, country_code: "US" and jurisdiction: "CA" on v1, or the same fields in camelCase on the 2026-07-21 release.
  • Expect a missing or unknown certificate type, another country or another state to be refused: 422 on v1, 400 with code invalid_request on the 2026-07-21 release.
Kintsugi API Changelog: 2026