curl --request POST \
--url https://api.example.com/admin/word/rules/filter \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"wordIDs": [
1,
2,
3,
4,
5
],
"forViewingInLanguageID": 1,
"applyToAllLanguages": null,
"languageIDs": [
1,
2,
3,
4,
5
],
"positionUsageTypeIDs": [
1,
2,
3,
4,
5
],
"actionTypeIDs": [
1,
2,
3,
4,
5
],
"authorIserIDs": [
702,
784,
683
],
"wordCandidateListID": null,
"searchText": null,
"page": 1,
"pageSize": 10
}
'{
"success": true,
"data": "<unknown>"
}Gets the list supplied words usage rule
curl --request POST \
--url https://api.example.com/admin/word/rules/filter \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"wordIDs": [
1,
2,
3,
4,
5
],
"forViewingInLanguageID": 1,
"applyToAllLanguages": null,
"languageIDs": [
1,
2,
3,
4,
5
],
"positionUsageTypeIDs": [
1,
2,
3,
4,
5
],
"actionTypeIDs": [
1,
2,
3,
4,
5
],
"authorIserIDs": [
702,
784,
683
],
"wordCandidateListID": null,
"searchText": null,
"page": 1,
"pageSize": 10
}
'{
"success": true,
"data": "<unknown>"
}The access token received from the authorization server in the OAuth 2.0 flow.
the language that the caller wishes to review the merge in. This changes the word of the language itself in the result data.