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.