**Description**
POST /entities/properties/{property_id}/aliases/{language_code}
request payload
```
{
"aliases": [
"ALIAS_TEXT"
, ... ]
...
}
```
**Acceptance criteria:**
- The respective successful responses should present the list of aliases in a given language -- similar to the responses of
`GET /entities/properties/{property_id}/aliases/{language_code}
`.
- If there was no aliases in the given language before the successful request the response should use 201 code, otherwise 200.
**Error cases to consider**
<table>
<tr>
<th>
</th>
<th>HTTP response code</th>
<th>response payload</th>
</tr>
<tr>
<td>Property does not exist </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}"`
`"context": {
"property": "{property-id}"
}` }`
</td>
</tr>
<tr>
<td>Invalid language code </td>
<td>400</td>
<td>
`{ `"code": "invalid-language-code"
, `
`"message": "Not a valid language code: {language_code}"
}`
</td>
</tr>
<tr>
<td>Alias contains invalid characters</td>
<td>400</td>
<td>
`"code": "invalid-alias"`
`"message": "Not a valid alias: '{alias}'"`
`"context": {`
`
"alias": <alias>`
`}`
</td>
</tr>
<tr>
<td>Alias is empty </td>
<td>400</td>
<td>
`{ `"code": "alias-empty"
, `
`"message": "Alias must not be empty"
}`
</td>
</tr>
<tr>
<td>Alias list is empty </td>
<td>400</td>
<td>
`{ `"code": "alias-list-empty"
, `
`"message": "Alias list must not be empty"
}`
</td>
</tr>
<tr>
<td>Alias too long </td>
<td>400</td>
<td>
`{ `"code": "alias-too-long"
, `
`"message": "Alias must be no more than {limit} characters long"
, `
`"context": {
`
` "value": "{alias}",
`
` "character-limit": "{limit}"
} }``
`}`
</td>
</tr>
<tr>
<td>Alias duplicate </td>
<td>400</td>
<td>
`{ `"code": "duplicate-alias"
, `
`"message": "Alias list contains a duplicate alias: '{alias}'"
, `
`"context": {
"alias": "{alias}"
}}`}`
</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>Comment too long</td>
<td>400</td>
<td>
`{`"code": "comment-too-long"
, `
`"message": "Comment must not be longer than {limit} characters"
}`
</td>
</tr>
<tr>
<td>Property does not exist </td>
<td>404</td>
<td>
`"code": "property-not-found"`
`"message": "Could not find a property with the ID: {property_id}"`
</td>
</tr>
</table>
**Notes**
- Automated edit summaries similar as done for items: T335842
- client can provide additional edit metadata: mediawiki tags, edit summary text to append to the automated summary, and a bot edit flag, like in
`GET /entities/properties/{property_id}/alias/{language_code}
`
- Handle HTTP conditional request headers as in
`POST /entities/items/{item_id}/aliases/{language_code}
`
- Handle user authentication/authorization like in
`POST /entities/items/{item_id}/aliases/{language_code}
`