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

Breaking changes
Answers 409 when you approve a filing that is being recalculatedBreaking change
Breaking changeFilings

Approving a filing now answers 409 while the filing is being recalculated, instead of approving it on amounts that may be out of date. On the Tenanted releases the error code is recalculation_in_progress, a new value of the error code enum. The recalculation finishes within moments, so the same request succeeds when you retry it.

What to do
  • Handle 409 on an approval by waiting a few seconds and sending the same request again.
  • On the Tenanted releases, tell this 409 apart from the duplicate-period 409 by its code, and treat an unknown code as a failure rather than a retry.

2026-10-27

Breaking changes
Removes the filing enhanced data endpointsBreaking change
Breaking changeFilings

GET /filings/{filing_id}/enhanced-data and POST /filings/{filing_id}/enhanced-data/rebuild are no longer available on any Tenanted release, including integrations pinned to 2026-07-21 or 2026-10-06. Requests to them answer 404. Read a filing's totals from GET /filings/{filing_id}.

What to do
  • Stop calling GET /filings/{filing_id}/enhanced-data and POST /filings/{filing_id}/enhanced-data/rebuild.
  • Read filing amounts from GET /filings/{filing_id} instead.

2026-10-20

Breaking changes
Shows Kintsugi's own task files only as payment receiptsBreaking change
Breaking changeFilings

An attachment Kintsugi adds while working on your account is now visible to you only when it is the state's payment receipt for a balance that is paid. GET /attachments leaves every other such file out. GET /attachments/{attachment_id} and GET /attachments/{attachment_id}/download answer 404 for it, the same answer as an id that does not exist. Files you upload yourself are unchanged.

What to do
  • Treat 404 from the attachment endpoints as final for a file that is not shared with you, and do not retry it.
  • Read payment receipts from paymentConfirmationAttachmentIds on a PAID proposal outcome from GET /proposals.

2026-10-14

Breaking changes
Splits the filing submission into a draft PATCH and a mark-filed POST on 2026-10-06Breaking change
Breaking changeFilings

On Api-Version: 2026-10-06, PUT /filings/{filing_id}/submission no longer exists and answers 405. PATCH /filings/{filing_id}/submission saves the confirmation fields as a draft and leaves the filing status unchanged. POST /filings/{filing_id}/mark-filed stores any confirmation fields you send and marks the filing FILED. Neither takes action. Repeating a mark-filed request for a filing already filed with the same values answers 200 with the filing and does nothing more, where the PUT answered 409. Both new endpoints answer 409 when the filing is not in FILING or SUBMITTED status. 2026-07-21 keeps the PUT with action. On every Api-Version, amountAdjusted, amountFees, amountPenalties and amountDiscounts now answer 422 when sent as null; before, null was stored as 0.00. Send an amount, including "0.00", or leave it out. returnConfirmationId and paymentConfirmationId still clear when sent as null.

What to do
  • On Api-Version: 2026-10-06, call PATCH /filings/{filing_id}/submission to save a draft and POST /filings/{filing_id}/mark-filed to mark the filing filed.
  • Retry mark-filed after a timeout without checking the filing first: an identical repeat answers 200.
  • Stop sending null for an amount. Send "0.00" for zero, or leave the amount out.

2026-10-08

Breaking changes
Removes retail delivery fee fields from v1 filings and registrationsBreaking change
Breaking changeFilings

A retail delivery fee is now its own registration and its own filing, so v1 no longer returns the fields that flagged it on a sales tax record. is_rdf is gone from filing responses, and retail_delivery_fee_obligated and retail_delivery_fee_effective_from are gone from registration responses. Read tax_type instead: a retail delivery fee registration or filing has tax_type RETAIL_DELIVERY_FEE, and it appears beside the state's sales tax record rather than inside it. On POST /v1/registrations for Colorado, retail_delivery_fee_obligated still asks for a retail delivery fee registration, opened beside the sales registration, but the value is no longer stored or returned on the sales registration. It is available to paid organizations with this feature enabled; for any other organization, a request that sets it answers 400.

What to do
  • Stop reading is_rdf, retail_delivery_fee_obligated and retail_delivery_fee_effective_from from v1 responses.
  • Identify a retail delivery fee filing or registration by tax_type RETAIL_DELIVERY_FEE.

2026-10-05

Breaking changes
Limits pausing a filing to the window before its due dateBreaking change
Breaking changeFilings

Pausing a filing now follows the same window as the Kintsugi app. After the 15th of the month a filing is due, it can no longer be paused with any pauseIntent, including assistance and skip, which were accepted before. A review pause also needs a pausedUntilDate from today through the 15th of the due month; a date in the past, accepted before, is now refused. A date that is still today anywhere in the world counts as today. POST /filings/{filing_id}/pause answers a refused pause with 400 and code invalid_request, and POST /filings/bulk/pause still answers 200, listing each refused filing in failed.

What to do
  • Pause a filing no later than the 15th of the month it is due.
  • For a review pause, send a pausedUntilDate no earlier than today and no later than the 15th of the due month.
  • After a bulk pause, check failed for filings that were not paused.
Kintsugi API Changelog: 2026