422 Unprocessable entity

[denizdogan]

For some reason this started today. I'm using the exact sample as in the documentation:

curl -X POST https://jsonbin.org/denizdogan/blog \
     -H 'authorization: token <redacted>' \
     -d '{ url: "https://remysharp.com" }'

Any ideas?

[psotos]

It's happening for me as well. I am adding in the content-type of application/json. With or without that it fails.

curl --location --request POST 'https://jsonbin.org/psotos/blog'
--header 'Content-Type: application/json'
--header 'authorization: token '
--header 'Cookie: id=
--data-raw '{
"org": "my org"
}'

[rektdeckard]

Getting the same! On inspection, the data is being written just fine -- but not returning 200.

[pke]

@remy this seems to still happen. Nothing It is saved, the request data is valid but the server response is 422.

Any ideas or can we get more debugging information?

[jyydev]

Same here. The data is successfully saved in json, just giving 422 status code in console.log after the POST request.

[Varun-Patkar]

Got the same error. Data gets added but response is 422

[iamcco]

Same here

[mboveiri]

same here

[pke]

@remy what do you think, could you address the issue? It's currently impossible to store arrays on the server.

[remy]

I'm soooper late replying (literally years later), but I couldn't replicate this using the first example.

Is there data already at the endpoint and you're trying to push or is it that you're trying to start an array?

[Pipth]

On my case I a trying to patch data on the endpoint (to change the contents) but I can't.

[remy]

@Pipth do you have a curl example (with your token removed) that I can use to replicate?

[innowesley]

@remy

curl -X PATCH "https://jsonbin.org/me/data/metadata"
-H "Content-Type: application/json"
-H "[OTHER HEADERS]"
-d '{"version": "1.0"}'

[ythong]

same here

[ythong]

POST is error， and Get is OK.

[ythong]

When I first registered (around September 2022), it was good. Later, due to the large content, the author helped me clear it a few days ago. Now I have discovered this problem.

[remy]

@ythong can you share the specific code (with the API token removed) that you're seeing the error with? Similar to what @innowesley has done.