As a tool developer I want to add statements to properties so that users of my tool can model properties in their Wikbase
POST /entities/properties/{property_id}/statements
**Notes**
- Handle HTTP conditional request headers as in POST /entities/items/{item_id}statements
- Handle user authentication/authorization like in POST /entities/items/{item_id}statements
**Error cases to consider**
<table>
<tr>
<th>
</th>
<th>HTTP response code</th>
<th>response payload</th>
</tr>
<tr>
<td>Property does not exist, either a "statement subject" property or a property used in the statement</td>
<td>404</td>
<td>
`"code": "property-not-found"`
`"message": "Could not find a property with the ID: {property_id}"`
</td>
</tr>
<tr>
<td>Invalid property ID</td>
<td>400</td>
<td>
`"code": "invalid-property-id"`
`"message": "Not a valid property ID: {property_id}"`
</td>
</tr>
<tr>
<td>Invalid edit tag</td>
<td>400</td>
<td>
`"code": "invalid-edit-tag"`
`"message": "Invalid MediaWiki tag: {tag}"`
</td>
</tr>
<tr>
<td>Edit comment/summary too long</td>
<td>400</td>
<td>
`"code": "comment-too-long"`
`"message": "Comment must not be longer than {limit} characters"`
</td>
</tr>
<tr>
<td>Data of a statement missing mandatory field</td>
<td>400</td>
<td>
`"code": "statement-data-missing-field"`
`"message": "Mandatory field missing in the statement data: '{field}'"`
`"context": { "path": "{field}"}`
</td>
</tr>
<tr>
<td>Value provided in statement data is invalid</td>
<td>400</td>
<td>
`"code": "statement-data-invalid-field"`
`"message": "Invalid input for '{field}'"`
`"context": { "path": "{field}", "value": "{value}"}`
</td>
</tr>
</table>
**Possibly relevant pointers:**
* Suggestion in 2020 Wikibase REST API proposal: ...
* How Wikibase Action API handles this: ...