Templates

A listing, a review and a chat message are not judged alike. A phone number is expected in one and a violation in another, and only a listing has a price to check against its description. A template holds those choices for one kind of content, and each request names the template it is judged by: "template": "listing".

You create and edit templates in the dashboard, under Templates. The API reads them and tests them. No endpoint creates or changes one.

Read a template to see what its requests are held to.

curl https://api.useinfrared.com/v1/templates/listing \
  -H "Authorization: Bearer $INFRARED_KEY"

const response = await fetch("https://api.useinfrared.com/v1/templates/listing", {
  headers: { Authorization: `Bearer ${process.env.INFRARED_KEY}` },
});

const template = await response.json();

import os
import requests

response = requests.get(
    "https://api.useinfrared.com/v1/templates/listing",
    headers={"Authorization": f"Bearer {os.environ['INFRARED_KEY']}"},
)

template = response.json()

{
  "object": "template",
  "id": "tpl_64mYq4nD3NXNfu0gcdaMZa",
  "slug": "listing",
  "name": "Listing",
  "description": null,
  "status": "active",
  "built_in": false,
  "version": 2,
  "context": "A public listing on a marketplace: an item, a service, a property or a vehicle for sale or rent, with a price and photos of what is offered. Buyers contact the seller through the platform.",
  "fields": [
    {
      "key": "title",
      "name": "Title",
      "type": "text",
      "required": true,
      "triggers": [
        { "effect": "flag", "policy": "hate_speech" },
        { "effect": "flag", "policy": "links_contact" }
      ],
      "validation": { "max_length": 120, "min_length": 5 },
      "description": "Short headline naming what is offered."
    } // description, price and photos follow
  ],
  "policies": [
    { "key": "toxicity", "mode": "trigger" },
    { "key": "links_contact", "mode": "trigger", "options": { "off_platform_phrases": true } },
    { "key": "gibberish", "mode": "trigger", "effect": "review" },
    { "key": "made_with_ai", "mode": "trigger", "effect": "review", "threshold": 0.9 },
    { "key": "guideline/no-off-site-deals", "mode": "trigger" } // 14 more
  ],
  "triggers": [
    { "effect": "flag", "policy": "hate_speech" },
    { "effect": "review", "policy": "duplicate" } // 5 more
  ],
  "rules": [
    {
      "id": "r6",
      "name": "Links from new accounts",
      "action": "review",
      "enabled": true,
      "conditions": [
        { "op": "at_most", "type": "author_trust", "value": "new" },
        { "type": "policy_flagged", "value": true, "policy": "links_contact" }
      ]
    } // r1 to r5 come first
  ],
  "severity": { "reject": 0.8, "review": 0.4 },
  "ai_instructions": "Check that the title, description, price and photos describe the same offer, ...", // trimmed
  "settings": {},
  "created_at": "2026-10-08T08:44:31.624Z",
  "updated_at": "2026-10-08T09:28:01.454Z"
}

The response is the published version of the template. Each part of it is a tab of the editor in the dashboard.

What a template holds

The Test tab holds no configuration. It runs a sample through the template and shows the verdict and the JSON your integration would receive.

Create a template

1. Name it

   Open Templates and choose New. Give the template the name of the content it moderates: Listings, Reviews, Messages. The slug your requests use is generated from that name.

2. Pick a starting point

   Under Start from, choose one of the eight presets or Blank template. A preset fills in fields, policies, triggers and rules for that kind of content. Listing is selected until you choose another. Then choose Create template.

   

3. Shape it, test it, publish it

   The editor opens on a draft, and nothing runs yet: a request that names the template answers 409 template_not_published. Adjust the tabs, try a sample in Test, then choose Publish version. From then on every edit goes to a new draft and waits for the next publication, as Versions, testing and diff describes.

The slug

• It is generated from the name when the template is created: lowercase letters, digits and hyphens, 2 to 80 characters. "Job postings" becomes job-postings.
• It is unique in the project. A slug that is taken gets a number: listing-2. An archived template keeps its slug, and basic belongs to the basic check.
• It never changes. Rename, in the More menu beside the editor's buttons, changes the name and the description only, so requests keep working.
• You cannot type or edit a slug. Create the template under the name that gives the slug you want, then rename it.

Draft, active, archived

Editing an active template does not change its status. The edits wait in a draft, marked with a second Draft badge in the list, and requests keep running the published version.

A template cannot be deleted. Archive template, in the More menu, takes it out of use and keeps every version. Switch on Show archived above the list to see it again, and choose Restore template to put it back to work.

Which template a request runs

1. The template the request names.
2. With no template, the project's default template.
3. With no default, the basic check.

The default is set in Settings, Project, under Default template. The list there also offers templates that were never published: with one of those as the default, every request that names no template answers 409 template_not_published. A default that is archived later is skipped without an error, and those requests run the basic check.

A named template is never swapped for another one. When it cannot run, the request fails.

A request that names listings in a project whose template is listing:

{
  "error": {
    "code": "template_not_found",
    "message": "Template listings not found",
    "details": [],
    "request_id": "req_cc04a628577f4e5a92c4f8b683c73b6b"
  }
}

Every moderation says which template and version judged it, in template: { "slug": "listing", "version": 2 }.

Templates over the API

Three things to know when you read templates:

• The list is not paginated. limit and cursor are accepted, and every template still comes back in one response. Archived templates are left out unless you ask with status=archived.
• GET /v1/templates/{slug} returns an archived template too, with "status": "archived".
• A template that was never published comes back with "version": null and none of the configuration keys. The API never returns a draft.

Plans and roles

The limit counts the templates of one project that are not archived. The basic check is not counted.

Owners, Admins, Project admins and Developers can create, edit, publish and archive templates. A Moderator can open them and sees Read only. Choosing the default template takes an Owner, an Admin or a Project admin. Members and roles has the full table.

Next

• Fields and validationA template's fields say what a submission must contain. Validation runs first, costs nothing and answers with one error per problem, named by field.
• TriggersA trigger says what a policy's score sets off, a flag or a review, for the whole template or for one field. One of your own replaces the default.
• PresetsEight starting points for a template, one per broad kind of content. Each fills in fields, policies, triggers and rules that you then make your own.
• Versions, testing and diffEdits go to a draft, a test runs it and keeps nothing, and publishing makes it the version every request runs. Earlier versions stay comparable.