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

Breaking changes
Requires a non-empty userId for imports started with an API keyBreaking change
Breaking changeImports

On POST /imports/initiate and POST /imports/upload-urls, whether you send userId now depends on your credential. With an API key it is required and must not be blank: a missing userId answers 400 with code invalid_request instead of 422, and an empty or whitespace-only value, accepted before, is now refused the same way. With a signed-in user session, userId is optional and ignored, and the import is recorded under that user.

What to do
  • With an API key, always send a non-empty userId that names the person or process uploading.
  • Expect 400 with code invalid_request, not 422, when userId is missing.
Kintsugi API Changelog: 2026