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

Breaking changes
Removes selfManaged from POST /registrationsBreaking change
Breaking changeRegistrations

POST /registrations no longer accepts selfManaged. A request that still sends it succeeds and the value is ignored, so every registration is created awaiting validation, as a request without selfManaged always was.

What to do
  • Stop sending selfManaged on POST /registrations.
  • Remove selfManaged from request models generated from the earlier spec.

2026-11-16

Breaking changes
Removes sltr_elected and single_local_tax_rate from the Texas fields on POST /v1/registrationsBreaking change
Breaking changeRegistrations

The Texas jurisdiction_specific_fields on POST /v1/registrations no longer include sltr_elected or single_local_tax_rate. Requests that still send them succeed, and the values are ignored, so a Texas registration created on v1 does not elect the single local tax rate.

What to do
  • Stop sending sltr_elected and single_local_tax_rate for Texas registrations.
  • Remove both fields from request models generated from the earlier v1 spec.

2026-11-06

Breaking changes
Limits who can reveal or overwrite stored registration credentials on v1Breaking change
Breaking changeRegistrations

Using reveal on GET /v1/registrations/{registration_id}, and sending a value for or clearing a credential that is already stored on PUT /v1/registrations/{registration_id}, now need an Owner of the organization or a Kintsugi Portfolio user who can open it. An API key counts as the user it belongs to, and a service key as the user who created it. Any other caller, and any automated assistant integration, gets 403, even when the PUT sends the value that is already stored. Before, any caller who could read or edit the registration could do both. The credentials covered are the username, password, security questions and portal access codes. A caller who can edit the registration can still fill a credential that has no stored value, except that a stored password also protects the username and security questions. Without reveal, credential fields come back masked.

What to do
  • Handle 403 from GET /v1/registrations/{registration_id} when you send reveal, and from PUT /v1/registrations/{registration_id} when the body sets or clears a stored credential.
  • Use credentials that belong to an Owner of the organization, or a service key, for integrations that reveal or replace stored credentials.
  • Stop sending credential fields back unchanged on PUT /v1/registrations/{registration_id}, since that is refused when a value is stored.
Requires an Owner behind an organization API key that reads or changes registration credentialsBreaking change
Breaking changeRegistrations

POST /registrations/{registration_id}/credentials/reveal, PUT and PATCH /registrations/{registration_id}/credentials and POST /registrations/{registration_id}/send-password now accept an organization's own API key only while an Owner stands behind it: the user the key belongs to or, for a key with no user, the user who created it. Before, any key for the organization could. Other keys get 403. An Owner is checked against their current role, so an Owner who is demoted or removed loses access at once instead of when their sign-in token expires. When the role cannot be confirmed, the endpoints answer 503 with a Retry-After header.

What to do
  • Create the API keys that call these endpoints as an Owner of the organization, or use a service key created by an Owner.
  • Handle 403 from these endpoints for a key whose user is not an Owner.
  • On 503, wait for the Retry-After delay and send the request again.

2026-10-14

Breaking changes
Updates registration credentials with PATCH on 2026-10-06 and lets null clear a credentialBreaking change
Breaking changeRegistrations

On Api-Version: 2026-10-06, PATCH /registrations/{registration_id}/credentials replaces PUT, which now answers 405. A credential you leave out keeps its stored value, and null clears it. That covers username, password, pin and securityQuestions, where null or [] clears the stored set. In jurisdictionSpecificFields, a string sets cdtfaThirdPartyAccessSecurityCode or accessCode and null clears that key, while null for the whole object answers 422. PUT ignored null, so it could never clear a credential. 2026-07-21 keeps PUT with its previous behavior, where null and an empty securityQuestions list leave the stored values unchanged.

What to do
  • On Api-Version: 2026-10-06, call PATCH instead of PUT to save credentials.
  • Send null only for a credential you want removed, and leave out every credential you want to keep.

2026-10-13

Breaking changes
Rejects null on replace-only registration fields and a lone createFilingsFromBreaking change
Breaking changeRegistrations

PATCH /registrations/{registration_id} now answers 422 when filingFrequency, autoRegistered, doNotFile, isPreCollecting, registrationsRegime or changeRegimeStatus is sent as null. Those fields only change when you send a value; before, a null was cleared or failed with a server error. Dates, timestamps and free-text fields still clear when sent as null. Where Kintsugi derives the first filing period, createFilingsFrom is recalculated when filingFrequency or registrationDate changes, and sending createFilingsFrom without either change now answers 400 instead of succeeding and being ignored. This applies to every Api-Version.

What to do
  • Stop sending null for filingFrequency, autoRegistered, doNotFile, isPreCollecting, registrationsRegime and changeRegimeStatus. Leave a field out to keep its value.
  • Do not send createFilingsFrom on its own. Change filingFrequency or registrationDate and read the recalculated value from the response.

2026-10-09

Breaking changes
Replaces the Colorado retail delivery fee flag with tax_type on registration importBreaking change
Breaking changeRegistrations

POST /v1/registrations now takes tax_type for every jurisdiction, defaulting to SALES_TAX, and no longer reads retail_delivery_fee_obligated. A Colorado request that sets only retail_delivery_fee_obligated is created as a sales tax registration and no retail delivery fee registration opens. To import a retail delivery fee registration, send tax_type RETAIL_DELIVERY_FEE: it opens beside the organization's existing sales tax registration in that state, which must not be cancelled or deregistered, and a request without one answers 400. A tax_type the jurisdiction does not allow also answers 400. GET /v1/registrations/jurisdiction-specific-fields now returns tax_types, the values you can send for that jurisdiction: SALES_TAX is always listed, and USE_TAX, SALES_AND_USE_TAX and RETAIL_DELIVERY_FEE appear where the jurisdiction and your organization support them.

What to do
  • Replace retail_delivery_fee_obligated: true with tax_type RETAIL_DELIVERY_FEE, and import the state's sales tax registration first.
  • Read tax_types from GET /v1/registrations/jurisdiction-specific-fields to see which values a jurisdiction accepts.

2026-09-22

Breaking changes
Requires a request body to deregister a registrationBreaking change
Breaking changeRegistrations

Deregistering now records when and why the registration closes. POST /v1/registrations/{registration_id}/deregister requires a JSON body with closure_date, reason and final_return_acknowledged, so a request with no body, which succeeded before, is now rejected with 422. The 2026-07-21 release changed the same way, with the fields closureDate, reason and finalReturnAcknowledged.

What to do
  • Send closure_date: the date the registration closes with the jurisdiction, as YYYY-MM-DD. Past and future dates are accepted.
  • Send reason: FULL_BUSINESS_CLOSURE or CLOSING_NEXUS_IN_STATE.
  • Send final_return_acknowledged: true, confirming that a final return is still owed.
Kintsugi API Changelog: 2026