I had a query that was working fine. Suddenly toda...
# help
a
I had a query that was working fine. Suddenly today, without any changes, I got a 422 error. (meaning unprocessable content!?)
1
x
Hi Atal, thanks for reaching out and sorry for the issues. Will check this out later
👍 1
Hi @Atal Atal, you need to use
job_id_or
instead of
job_ids
in the body of the request. We changed it to
job_id_or
and as the response says, we don’t allow unexpected fields in the body. I see you’re passing an empty list, so you could remove that part altogether. Sorry that this disrupted you, we thought no one was using this parameter
We’ve allowed that field again so that requests from other users don’t fail too, but marked it as deprecated in the API docs: