Actions

An action is what a decision becomes: allow, reject, a change of an author's status, or an operation you define, such as asking a seller to edit a listing. A reviewer runs one from an item of the review queue. Your backend runs one through the API.

Infrared changes nothing in your product. Running an action applies its effect inside Infrared (the queue item, the author's status), writes a log entry and sends the action.executed webhook event. Your backend acts on that event.

Here a custom action, request_edits, runs on a listing that is waiting in the queue:

curl https://api.useinfrared.com/v1/actions/request_edits/execute \
  -H "Authorization: Bearer $INFRARED_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "moderation_id": "mod_6IYSa2qBKpMi4Xnxm1jkOB",
    "value": {
      "reason": "off_platform_link",
      "message": "Remove the link from the description."
    },
    "note": "Second listing from this seller with an outside link."
  }'

const response = await fetch("https://api.useinfrared.com/v1/actions/request_edits/execute", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.INFRARED_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    moderation_id: "mod_6IYSa2qBKpMi4Xnxm1jkOB",
    value: {
      reason: "off_platform_link",
      message: "Remove the link from the description.",
    },
    note: "Second listing from this seller with an outside link.",
  }),
});

const log = await response.json();

import os
import requests

response = requests.post(
    "https://api.useinfrared.com/v1/actions/request_edits/execute",
    headers={"Authorization": f"Bearer {os.environ['INFRARED_KEY']}"},
    json={
        "moderation_id": "mod_6IYSa2qBKpMi4Xnxm1jkOB",
        "value": {
            "reason": "off_platform_link",
            "message": "Remove the link from the description.",
        },
        "note": "Second listing from this seller with an outside link.",
    },
)

log = response.json()

{
  "object": "action_log",
  "id": "al_2vl5zS0SnY5XqWDjRROnpk",
  "action_id": "act_2BdP4rjezzQ5PTND66nyLi",
  "action": "request_edits",
  "target_type": "moderation",
  "moderation_id": "mod_6IYSa2qBKpMi4Xnxm1jkOB",
  "author_id": null,
  "queue_item_id": "qi_0eietVVV87wOZub5qkiPfU",
  "actor_user_id": null,
  "source": "api",
  "value": {
    "reason": "off_platform_link",
    "message": "Remove the link from the description."
  },
  "note": "Second listing from this seller with an outside link.",
  "created_at": "2026-10-08T08:48:22.177Z"
}

Built-in actions

Every project starts with five.

block_author and suspend_author accept a value: a string is the reason, an object is { "reason": "...", "until": "2026-10-13T00:00:00Z" }. Only suspend_author reads until.

A built-in can be renamed, hidden from the dashboard or disabled, never deleted. Disabling allow or reject makes the Allow and Reject buttons of the queue, and resolution in the API, answer 409 action_disabled.

Custom actions

A custom action names something your product does: request edits, hide a listing, warn a seller. Create it in the dashboard under Actions, with Create action. The API runs actions and does not create or edit them.

Infrared does not check a value: whatever JSON a run carries goes to the log and the webhook as it is. Validate it in your handler. The value_schema field of an action object is not used today.

Run an action

In the dashboard, actions run from a queue item: Allow and Reject are buttons, the rest are under More actions. The Actions page itself has no run button.

Through the API, name the action in the path and say what it runs on.

GET /v1/actions lists the project's enabled actions, hidden ones included.

Execute ignores the Idempotency-Key header, so a retried request runs the action again and sends the event again. Make your handler safe to run twice.

What your backend receives

The run above sent this event:

{
  "id": "evt_4m24Cq6qE5xjatO20hxDK6",
  "type": "action.executed",
  "created_at": "2026-10-08T08:48:22.365Z",
  "api_version": "2026-09-01",
  "data": {
    "value": {
      "reason": "off_platform_link",
      "message": "Remove the link from the description."
    },
    "action": {
      "id": "act_2BdP4rjezzQ5PTND66nyLi",
      "key": "request_edits",
      "name": "Request edits",
      "target": "content",
      "built_in": false,
      "accepts_value": true,
      "queue_behavior": "resolve"
    },
    "source": "api",
    "author_id": null,
    "content_id": "listing_20932",
    "executed_at": "2026-10-08T08:48:22.177Z",
    "moderation_id": "mod_6IYSa2qBKpMi4Xnxm1jkOB",
    "queue_item_id": "qi_0eietVVV87wOZub5qkiPfU"
  }
}

data.action is the whole action object, shortened here, and content_id is the id you sent with the moderation. source is api or dashboard.

author_id is Infrared's id of the author, starting with aut_, not the id you use. The API looks authors up by your id only, so keep both ids from the moderation response, or send yours in value.

Other events can come first. An action that resolves a queue item sends queue_item.allowed, queue_item.rejected or queue_item.actioned before it: this run sent queue_item.actioned, with the resolution action:request_edits. A built-in author action sends author.blocked, author.suspended or author.enabled before it.

A status change made on an author's page or with the author endpoints is not an action. It sends its author.* event only, so follow status through those events, not through action.executed.

The action log

Every run adds one entry, and entries never change. Recent executions on the Actions page lists them with the action, the target, the source, the note and who ran it. An author's page lists the runs on that author.

The API returns the entry as the answer to execute and has no endpoint that lists the log. GET /v1/webhooks/events?type=action.executed lists the same runs as events for 30 days, whether or not a webhook endpoint exists.

Who can do what

In the dashboard, creating, editing, disabling and deleting an action needs the Developer role or one above it. Any member can run an action from a queue item. An API key needs the read scope to list actions and the write scope to execute one.

Next

• Review queueContent your rules send to review waits in the queue until a person, or your own code, allows it, rejects it or runs another action on it.
• Event typesThe twelve events Infrared sends, when each one fires and what its data holds, with a real payload for moderations, queue items, authors and actions.
• Authors and trustInfrared keeps a status, a trust level and a history for each of your users, and content rules read them. Block, suspend or trust an author.
• Verify signaturesEvery delivery is signed with the endpoint's secret. Check the signature and its timestamp before you trust the body, with code you can copy.