The OOPSpam API takes an optimistic approach and avoids blocking messages unless it’s confident they are spam. However, false positives (legitimate messages marked as spam) and false negatives (spam messages marked as legitimate) can still occur. There are various reasons for false positives and false negatives, such as:

IP addresses previously used for spamming but now in different hands, retaining a bad reputation. Messages incorrectly flagged as blocked or not blocked.

To minimize these occurrences, it’s essential to train the OOPSpam API’s standard model with the specific spam and non-spam (ham) messages you’re receiving. This process will improve the model’s accuracy over time, reducing false positives and false negatives.

Reporting False Positives and False Negatives

Depending on the plugin you’re using, there are several ways to report false positives and false negatives to the OOPSpam model:


The API users, should use the Report endpoint documented here to report any false positives and false negatives. The status of the reported items can be viewed at the Reported page in the OOPSpam Dashboard.


Use the Form Spam Entries and Form Ham Entries option to report false positives and false negatives.


  1. Set the Log submissions to OOPSpam parameter to true. For, set logIt to true in the request body. Refer to the Spam Detection documentation for more information on request body parameters.

OOPSpam Zapier app

  1. This will enable you to view and report all submissions on the Logs page in the OOPSpam dashboard. Click Flag as spam or Flag as ham to flag an entry as a false positive or false negative, respectively.

OOPSpam Logs

  1. The flagged items will be available under the Reported page.