ClearTalk Anti-Spam filter API — screenshot of cleantalk.org
cleantalk.org ·

ClearTalk Anti-Spam filter API

This API provides a straightforward method to check messages and comments from my service for spam, especially useful for user-generated content. It integrates anti-spam capabilities into forms via a POST request, returning a decision.

Visit cleantalk.org →

Questions & Answers

What is the CleanTalk Anti-Spam check_message API?
The CleanTalk Anti-Spam "check_message" API is a method for programmatically checking user-generated content, such as comments or messages, for spam. It receives form data via a POST request and returns a decision on whether the content is spam.
Who should use the CleanTalk Anti-Spam check_message API?
This API is ideal for developers and service providers who need to integrate anti-spam capabilities directly into their web applications, especially for forms handling user-generated content like comments, reviews, or contact forms.
How does CleanTalk's check_message API compare to other anti-spam solutions?
The CleanTalk API provides a direct server-side check without requiring CAPTCHAs, relying on various parameters like sender IP, email, and message content, potentially supplemented by client-side bot detection. It offers a detailed response with specific codes explaining the spam decision.
When is the best time to implement the check_message API?
It should be used on forms that collect user-generated content, such as comments sections, review submission forms, or general contact forms, before the content is saved or published, to prevent spam from entering the system.
What are the key technical parameters for using the check_message API?
The API requires "method_name" ("check_message"), "auth_key", and typically "sender_email", "sender_nickname", "sender_ip", and the "message" content. It supports additional parameters like "event_token" for enhanced bot detection.

More from Coding