Record which moderator allowed or rejected content in your own tool, and add the decision to your casebook.

If your team reviews content in its own tool, you send the result to us with an allow or reject action. Until now, that action was not recorded as any person's, and it never became a casebook case.

Now you can name the moderator, and the decision counts the same as one made in the review inbox.

await client.content.reject({
  id: 'post-123',
  body: { reason: 'Spam', moderator: '[email protected]' },
});

How it works

• moderator takes the user ID or email of a member of your organization. The action is recorded as theirs. If no member matches, the request fails with a 400 error.

• createCasebookCase controls the casebook. A decision with a moderator becomes a case by default. Set it to true to add a decision without a moderator, which is recorded as System. Set it to false to keep a decision out.

• Both fields work on content.allow(), content.reject() and actions.execute().

Calls that send neither field work as before. Automated actions stay out of your casebook.