Profanity Checker
Pricing
$0.25 / 1,000 processed texts
Check comments, reviews, messages, and text snippets for blocked words. Clean text and export match evidence for content moderation workflows.
Pricing
$0.25 / 1,000 processed texts
Rating
0.0
(0)
Developer
Maxime Dupré
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
8 days ago
Last modified
Categories
Share
You can access the Profanity Checker programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.
# Set API token$API_TOKEN=<YOUR_API_TOKEN>
# Prepare Actor input$cat > input.json << 'EOF'<{< "texts": [< "Default QA 1: please hide this shit before export.",< "Default QA 2: clean text without blocked words.",< "Default QA 3: this damn message is allowed to mask, but damnation stays safe.",< "Default QA 4: clean text without blocked words.",< "Default QA 5: spoiler should be caught by custom words.",< "Default QA 6: this damn message is allowed to mask, but damnation stays safe.",< "Default QA 7: please hide this shit before export.",< "Default QA 8: clean text without blocked words.",< "Default QA 9: this damn message is allowed to mask, but damnation stays safe.",< "Default QA 10: spoiler should be caught by custom words.",< "Default QA 11: please hide this shit before export.",< "Default QA 12: this damn message is allowed to mask, but damnation stays safe.",< "Default QA 13: please hide this shit before export.",< "Default QA 14: clean text without blocked words.",< "Default QA 15: spoiler should be caught by custom words.",< "Default QA 16: clean text without blocked words.",< "Default QA 17: please hide this shit before export.",< "Default QA 18: this damn message is allowed to mask, but damnation stays safe.",< "Default QA 19: please hide this shit before export.",< "Default QA 20: spoiler should be caught by custom words.",< "Default QA 21: this damn message is allowed to mask, but damnation stays safe.",< "Default QA 22: clean text without blocked words.",< "Default QA 23: please hide this shit before export.",< "Default QA 24: this damn message is allowed to mask, but damnation stays safe.",< "Default QA 25: spoiler should be caught by custom words."< ],< "customWords": [< "spoiler"< ],< "allowedWords": [< "damnation"< ]<}<EOF
# Run the Actor using an HTTP API# See the full API reference at https://docs.apify.com/api/v2$curl "https://api.apify.com/v2/acts/maximedupre~profanity-checker/runs?token=$API_TOKEN" \< -X POST \< -d @input.json \< -H 'Content-Type: application/json'Below, you can find a list of relevant HTTP API endpoints for calling the Profanity Checker Actor. For this, you’ll need an Apify account. Replace <YOUR_API_TOKEN> in the URLs with your Apify API token, which you can find under Integrations in Apify Console. For details, see the API reference.
https://api.apify.com/v2/acts/maximedupre~profanity-checker/runs?token=<YOUR_API_TOKEN>Note: By adding the method=POST query parameter, this API endpoint can be called using a GET request and thus used in third-party webhooks. Please refer to our Run Actor API documentation.
https://api.apify.com/v2/acts/maximedupre~profanity-checker/run-sync-get-dataset-items?token=<YOUR_API_TOKEN>Note: This endpoint supports both POST and GET request methods. However, only the POST method allows you to pass input data. For more information, please refer to our Run Actor synchronously and get dataset items API documentation.
https://api.apify.com/v2/acts/maximedupre~profanity-checker?token=<YOUR_API_TOKEN>For more information, please refer to our Get Actor API documentation.
Actors can be used to scrape web pages, extract data, or automate browser tasks. Use the Profanity Checker API programmatically via the Apify API.
You can choose from:
You can start Profanity Checker with the Apify API by sending an HTTP POST request to the Run Actorendpoint. An Actor’s input and its content type can be passed as a payload of the POST request, and additional options can be specified using URL query parameters. The Profanity Checker is identified within the API by its ID, which is the creator’s username and the name of the Actor.
When the Profanity Checker run finishes you can list the data from its default dataset(storage) via the API or you can preview the data directly on Apify Console.