Relates to `GET /entities/items/{item_id}/statements/{statement_id}` and `GET /entities/properties/{property_id}/statements/{statement_id}` routes
The statement ID contains the ID of the item or the property which is the "subject" of the statement.**Description:**
The statement ID contains the ID of the item or the property which is the "subject" of the statement. If the ID of the "subject" and the ID of the item and property provided in the request path do not match, the input is clearly invalid and it is clear that the Wikibase REST API will not be able to process the request and the API can early stop processing the request.
We do not have to make potentially resource-consuming operations to validate if the item, or property actually exist. API can early stop processing the request and indicate the issue with the input.**Acceptance criteria:**
Suggested response: 400 error response
```
"code": "item-statement-id-mismatch" / "property-statement-id-mismatch"
"message": "IDs of the item and the statement do not match" / "IDs of the property and the statement do not match"
"context": { "item-id": "<ITEM_ID>", "statement-id": "<STATEMENT_ID>" } / { "property-id": "<PROPERTY_ID>", "statement-id": "<STATEMENT_ID>" }
```
**Notes:**
Endpoints this refers to:
This would apply to everything [[https://doc.wikimedia.org/Wikibase/master/js/rest-api/#/statements | here ]] EXCEPT:
* All POST
* GET all statements of an item or a property
* GET, PUT, PATCH, DELETE directly for statement
In addition:
* PATCH a property