PurgoMalum API

Beginner's Pick Data Validation / No Auth Required Beginner HTTP
Free to Use
55 C
Measured Score 0 50 100 Speed 8/30 Consistency 4/20 Security 20/20 Browser access 15/15 Transparency 8/15 TESTED 2026-08-10

Overview

PurgoMalum is a free, no-auth REST API for filtering profanity and obscene words from text, returning a cleaned version with offensive terms replaced by asterisks or a custom fill character. It works with plain HTTP GET requests — just pass the text as a query parameter — making it one of the simplest content moderation APIs available. A `containsprofanity` endpoint lets you check for profanity presence without transforming the text.

Beginner Tip

No API key needed. Pass text via the `text` parameter: `https://www.purgomalum.com/service/plain?text=your+text+here`. Use `/service/json` for a JSON response or `/service/xml` for XML. To use a custom replacement character instead of asterisks, add `&fill_char=X`. The API is GET-only and works directly from the browser address bar.

Measurement Record

What actually happened when we called this API from our own infrastructure. Every value below was recorded by the request, not copied from the provider's documentation.

Request
GET https://www.purgomalum.com/service/json?text=This+is+some+bad+text
Result
HTTP 200 · application/json · 34 bytes · compressed
Response time
395 ms (median of 3) · fastest 238 ms
Transport
TLSv1.3 · TLS_AES_256_GCM_SHA384 · certificate issued by Google Trust Services
Browser CORS
Allowed — Access-Control-Allow-Origin: *
Served by
Google Frontend
Recorded
2026-08-10

Fields Returned

Top-level fields present in the response we captured, with the type and value we actually received.

Field Type Value received
result string This is some bad text

Captured Response

Captured from a real request to https://www.purgomalum.com/service/json?text=This+is+some+bad+text on 2026-08-10. Long arrays and nested objects are truncated to keep the shape readable.

JSON Response · Captured
{
  "result": "This is some bad text"
}

Field Reference

result The input text with profanity replaced by asterisks (or your custom `fill_char`). Returned when using the `/service/json` endpoint.

Implementation Example

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request
const url = "https://www.purgomalum.com/service/json?text=This+is+some+bad+text";
const response = await fetch(url);
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

How This API Fails

We deliberately sent this API a broken request and recorded exactly what came back on 2026-08-10. Knowing the shape of an error before you hit it makes error handling much easier to write.

HTTP 404 Requesting a path that does not exist text/html

Returned an HTML error page rather than JSON — worth knowing if your client assumes every response can be parsed as JSON.

Common Errors & Troubleshooting

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

API returns the original text unchanged No profanity was detected in the input — PurgoMalum only modifies text containing words in its blocklist.
This is expected behavior. Use `/service/containsprofanity` endpoint to first check whether the text contains profanity before filtering.
Special characters are stripped or mangled Special characters in the text are not URL-encoded.
URL-encode the text before sending (e.g., spaces as `+` or `%20`). Use `encodeURIComponent()` in JavaScript or `urllib.parse.quote()` in Python.
Mixed-content browser warning PurgoMalum's primary URL uses HTTP, which modern browsers block when called from HTTPS pages.
Call the API server-side from your backend rather than directly from browser JavaScript to avoid mixed-content policy restrictions.

Measured Score Breakdown

Live HTTP request to the API endpoint

Speed 8/30
Consistency 4/20
Security 20/20
Browser access 15/15
Transparency 8/15
Endpoint Response Time 395ms

Fully tested on Aug 10, 2026

Technical Specifications

Auth No Auth
HTTPS NO
CORS UNKNOWN
Category Data Validation
Difficulty Beginner
Endpoint last called: 2026-08-10

Related Tags

Similar APIs

View All →