Ingest record
Create or update a content record for moderation asynchronously. Results are returned via a webhook event. To update a record, simply ingest the content again with the same clientId.
Authorization
AuthorizationRequiredBearer <token>Bearer authentication header of the form Bearer , where is your auth token.
In: header
Request Body
application/jsonRequiredclientIdRequiredstringA unique identifier for the record, assigned by the client. Used to create or update the record. The clientId must be unique for each record. This is usually your id for the record.
clientUrlstringAn optional URL associated with the record, such as a link to the original content.
nameRequiredstringThe name or title of the record.
entityRequiredstringThe category or type of the record (e.g., 'post', 'comment', 'message'). Helps categorize the content.
contentRequiredobjectmetadataobjectOptional metadata associated with the record. Keys must be strings, values can be of any type, but will be serialized to JSON.
userobjectOptional information about the user associated with the record. The user object allows all content for a given user to be grouped (and for suspension/ban actions to operate at a user level).
Record successfully created or updated.