# Handling Actions When Coop triggers an Action—whether through an automated rule, a moderator's decision in the Review Console, or a user crossing a User Strike threshold—it sends a POST request to the callback URL you configured for that Action. Your server receives this request and performs the corresponding operation. ## List actions ```http GET /api/v1/actions/ ``` Returns your organization's custom and built-in actions: ```json { "actions": [ { "id": "action-id", "name": "Remove post", "description": null, "actionType": "CUSTOM_ACTION", "applyUserStrikes": false, "penalty": "NONE", "itemTypeIds": ["item-type-id"], "parameters": [] } ] } ``` ## Setting up your callback endpoint For each Action you define in Coop, provide a publicly accessible callback URL and any authentication headers your endpoint requires (e.g. an API key Coop should send). Coop includes these headers on every outgoing request to that endpoint. To verify that an incoming request actually came from Coop, check the `Coop-Signature` header. See [API Keys & Authentication](../development/api-auth.md#verifying-incoming-requests-from-coop) for the signature verification algorithm and a code example. Failed deliveries are retried up to five times with exponential backoff. ## Request body ```json { "item": { "id": "item-id", "typeId": "item-type-id" }, "action": { "id": "action-id" }, "policies": [{ "id": "policy-id", "name": "Spam", "penalty": "MEDIUM" }], "rules": [{ "id": "rule-id", "name": "Spam detector" }], "custom": {}, "actorEmail": "moderator@example.com", "creator": { "id": "user-id", "typeId": "user-type-id" }, "decisionReason": "Violated spam policy", "userStrikeCount": 3 } ``` ### Field reference | Field | Type | Always present? | Description | | :---------------- | :-------------- | :-------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `item` | Item | Always | The item that should receive this Action | | `action` | Action | Always | The Action being triggered | | `policies` | Array\ | Always | Policies associated with this action. May contain multiple entries if several rules triggered the same action | | `rules` | Array\ | Not always | Rules that triggered this action. Empty if triggered via manual review or bulk actioning | | `custom` | Object | Not always | Custom parameters configured in the Action form under "Body". For Review Console decisions on reported items, Coop also merges `reason` and `reportHistory` into this object (see "Custom object" below) | | `actorEmail` | String | Not always | Email of the Coop user who took the action. Omitted for automated rule-triggered actions | | `actorNote` | String | Not always | Note added by the moderator when taking the action. Omitted if no note was provided | | `creator` | ItemIdentifier | Not always | The user the action concerns: the target itself for `USER` items, or the content's author for `CONTENT` items. Omitted when no creator can be resolved (e.g. a content id with no known submission) | | `decisionReason` | String | Not always | The moderator's decision reason, as supplied via the Review Console or Submit Decision API. Present for Review Console decisions that include a reason; omitted otherwise | | `userStrikeCount` | Number | Not always | The user's cumulative strike total after this action (existing strikes plus any applied by this event). Omitted when no target user can be resolved | **Item schema:** | Field | Type | Description | | :--------- | :----- | :---------------------------------- | | `id` | String | Your unique identifier for the item | | `typeId` | String | The Item Type ID | | `typeName` | String | The display name of the Item Type | **Policy schema:** | Field | Type | Description | | :-------- | :----- | :---------------------------------------------------------- | | `id` | String | Coop's unique policy ID | | `name` | String | Policy name | | `penalty` | String | Penalty level: `NONE`, `LOW`, `MEDIUM`, `HIGH`, or `SEVERE` | **Rule schema:** | Field | Type | Description | | :----- | :----- | :-------------------- | | `id` | String | Coop's unique rule ID | | `name` | String | Rule name | **Custom object:** Besides the parameters you configure under "Body", Coop merges the following into `custom` for Review Console decisions made on **reported** items. (The decision reason is also delivered as the top-level `decisionReason` field; it appears in both places.) | Field | Type | Description | | :-------------- | :-------------- | :----------------------------------------------------------------------------- | | `reason` | String | The moderator's decision reason (same value as the top-level `decisionReason`) | | `reportHistory` | Array\ | The reports filed against the item, each as `{ reason, reporter }` | ### User Strikes When a user's cumulative strike score crosses a configured threshold, Coop executes the action associated with that threshold using the same callback mechanism described above. The only differences from a rule-triggered action callback are: - `policies` is always an empty array; the threshold fires on cumulative score, not a specific policy violation in this request - `rules` is always an empty array; no rule directly triggered the callback - `actorEmail` and `actorNote` are never present; there is no human actor For more on setting up and configuring user strikes, thresholds, and associated actions, see [User Strikes](../user/automated-enforcement.md#user-strikes) in the user guide. ## Appeal decision callback When a moderator reviews an appeal in the Review Console and makes a decision, Coop sends a POST request to the Appeal callback URL configured in your Appeals Dashboard. ```json { "appealId": "your-appeal-id", "item": { "id": "item-id", "typeId": "item-type-id" }, "appealedBy": { "id": "user-id", "typeId": "user-type-id" }, "appealDecision": "ACCEPT", "custom": {} } ``` ### Appeal callback field reference | Field | Type | Always present? | Description | | :--------------- | :------------- | :-------------- | :----------------------------------------------------------------------------------------------------------- | | `appealId` | String | Always | Your internal appeal ID, as sent via the Appeal API | | `item` | Item | Always | The item that originally received the moderation action | | `appealedBy` | ItemIdentifier | Always | The user who submitted the appeal | | `appealDecision` | String | Always | `ACCEPT` means the original action was incorrect (appeal granted); `REJECT` means the original action stands | | `custom` | Object | Not always | Custom parameters configured in the Appeal Configuration Form under "Body" | For the full appeal submission flow, see [Appeals](../user/appeals.md).