In T342990#9874495, @Ollie.Shotton_WMDE wrote:

Hi @wassan.anmol117, yes, that is to be expected. Just like via the Wikidata UI, you can create anonymous edits that will be associated with an IP address (in the future this will be temporary anonymous accounts). If you want your edits to be associated with a particular account, then you would need to authenticate. There are other benefits to authenticating, such as an increased rate limit.

Change #1034838 merged by jenkins-bot:

[mediawiki/extensions/Wikibase@master] Handle invalid data value input

https://gerrit.wikimedia.org/r/1034838

Hi @wassan.anmol117, yes, that is to be expected. Just like via the Wikidata UI, you can create anonymous edits that will be associated with an IP address (in the future this will be temporary anonymous accounts). If you want your edits to be associated with a particular account, then you would need to authenticate. There are other benefits to authenticating, such as an increased rate limit.

Change #1040864 had a related patch set uploaded (by Dima koushha; author: Dima koushha):

[mediawiki/extensions/Wikibase@master] REST: Validate labels and descriptions in PatchItem use case

https://gerrit.wikimedia.org/r/1040864

Change #1039203 merged by jenkins-bot:

[mediawiki/extensions/EntitySchema@master] Register EntitySchema value deserializer

https://gerrit.wikimedia.org/r/1039203

@Ollie.Shotton_WMDE @Ifrahkhanyaree_WMDE While using the API, I observed that I was able to make a POST call with unauthenticated API requests. For example, I created this item on https://test.wikidata.org without the Authorization header and it worked. Is this expected?

Change #1037817 merged by jenkins-bot:

[mediawiki/extensions/Wikibase@master] Don't conflate snak parsing and deserializing

https://gerrit.wikimedia.org/r/1037817

Change #1037772 merged by jenkins-bot:

[mediawiki/extensions/Wikibase@master] Add 'deserializer-builder' to DataTypeDefinitions

https://gerrit.wikimedia.org/r/1037772

Change #1038784 abandoned by Jakob:

[mediawiki/extensions/WikibaseLexeme@master] Add new DeserializerFactory constructor arg

Reason:

changed approach, no longer needed

https://gerrit.wikimedia.org/r/1038784

Sure. Thanks @Ollie.Shotton_WMDE!

Ahh, right, yes! So what is happening here is that wikidata.org is redirected, via a "301 Moved Permanently" response, to www.wikidata.org. Postman is automatically following this redirect but changing the POST method to a GET method, hence the error you saw. You can see this redirect if you turn off Automatically follow redirects in Postman's settings. This is a client issue and not something we can change in the Wikibase REST API.

Change #1039733 had a related patch set uploaded (by Muhammad Jaziraly; author: Muhammad Jaziraly):

[mediawiki/extensions/Wikibase@master] REST: Validate aliases in PatchItem use case

https://gerrit.wikimedia.org/r/1039733

In T342990#9867087, @Ollie.Shotton_WMDE wrote:

Hi @wassan.anmol117,

What version of Postman are you using? Have you tried alternative tools, or something like curl on the command line?

This curl command returns a label-description-same-value error for me (as expected):

curl --request POST \
  --url https://www.wikidata.org/w/rest.php/wikibase/v0/entities/items \
  --header 'Content-Type: application/json' \
  --data '{ "item": { "labels": { "en": "test" }, "descriptions": { "en": "test" } } }'

What version of Postman are you using? Have you tried alternative tools, or something like curl on the command line?

Yes, I've selected that.

Hi @wassan.anmol117, it's live on Wikidata since yesterday. Have you explicitly selected the method to be POST when testing it on Postman? I think it needs that even after the body has been defined

@Ollie.Shotton_WMDE @Ifrahkhanyaree_WMDE Did this go live yesterday? I tried testing the API on Postman but it is giving me the following error even after I am sending a POST request: