{
"success": true,
"data": "<unknown>"
}Moderation events are where a user either validates or invalidates content, saving / updating flags, (which would cause the entity to show or hide), as well as perform adjudication for ‘approvable’ items (Category|Topic|Verb|Conjunction).
For some entity types, we provide adjudication information in the form of a word status type. These are Category|Topic|Verb|Conjunction.
OptionalWordStatusTypeID: (int)
1 = Proposed: Proposed to be created. This should really only happen in the system when an end-user proposes a verb or conjunction.2 = Approved: Approved, this would become active in the system.3 = Rejected: The item will be rejected and the iser who originally proposed it will be informed. This also may cause isms that leverage this item to become hidden.4 = Suspended: The item will be suspended and the iser who originally proposed it will be informed. This also may cause isms that leverage this item to become hidden.For all entity types, you must specify the ‘reason type’.
EntityHistoryReasonTypeID: (int)
1 = Violates Terms and Conditions: Rejected because it violates at least one of our terms and conditions of use.2 = Gibberish: Rejected because it appears to be random characters and makes no sense.3 = Incorrect spelling or grammar: Rejected because it could be incorrect spelling or grammar (aside from stylization). We don’t really want poorly formed verbs and conjunctions to proliferate. So unless it appears the user is intentionally spelling something the wrong way for stylization, it will be scrutinized.4 = Other: Rejected for another reason, which should be provided in the ‘Comment’ property.{
"success": true,
"data": "<unknown>"
}The access token received from the authorization server in the OAuth 2.0 flow.