An action is anything that can run against a piece of content or a user: rejecting a comment, blocking an author, sending a warning, removing a profile from your app. Each action is configurable, can carry a value (a reason, a category, a duration), and can fire a webhook so your application reacts in real time. Actions live in two flavors:Documentation Index
Fetch the complete documentation index at: https://docs.moderationapi.com/llms.txt
Use this file to discover all available pages before exploring further.
Content actions
Run on individual queue items. Built-in reject and allow, plus any custom actions you create — “Hide post”, “Send to legal”, “Flag for review”, etc.
Author actions
Run on the user behind the content. Built-in block, suspend, and enable, plus custom author-level actions like warnings or feature restrictions.
How actions are used
- In the dashboard. Moderators run actions from the queue or user detail pages. Custom actions appear alongside the built-ins.
- Programmatically. Call the execute action endpoint to run any action — built-in or custom — against content or authors from your own systems.
- As webhook triggers. Every action that runs fires a webhook event (
queue_item.rejected,author.blocked,queue_item.action, etc.) so you can sync state back to your application.
Built-in vs. custom
Built-in actions cover the common cases — rejecting content, blocking authors, and so on. If they don’t cover what you need, you can create custom actions to fit your workflow.| Built-in | Custom | |
|---|---|---|
| Created by | The system | You |
| Examples | Reject, allow, block, suspend, unblock | ”Hide post”, “Send warning email”, “Escalate” |
| Webhook event | Dedicated event per action (e.g. queue_item.rejected) | Generic queue_item.action or author.action |
| Configurable | Possible values, queue visibility | Everything: name, level, values, queue behavior |
What’s next
Content actions
Reject, allow, and custom item-level actions.
Author actions
Block, suspend, enable, and custom user-level actions.
Webhooks
Receive real-time events when actions run.