creator.lottiefiles.com

list_slots

List design-token slots defined in the file. Each slot has ONE stable id (e.g. 'brand-red') but can supply different VALUES per theme — Default theme might have brand-red as crimson, a Dark theme might have it as burgundy. The toolkit renders whichever value the currently active theme provides. Use before inventing hardcoded values whenever the user names a brand concept ('brand red', 'primary blue', 'the header color', 'our headline text'). Filter with `type` to narrow (e.g. COLOR for fill/stroke pickers, TEXT for headline strings). Returns `{ slots: [{ id, type, values_by_theme: { themeId: value, ... }, active_theme, active_value }] }`. Without `theme_id`, `active_value` is what the canvas renders right now. With a `theme_id` filter for an inactive theme, `active_value` may be that filtered theme's fallback value for inspection, while `active_theme` still names the canvas-rendered theme. The `values_by_theme` map shows variants if the user wants to recolor a specific theme. Empty `slots` means the file has no tokens of that type — fall back to inline values and say so.

Input schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "type": {
      "description": "Optional slot type filter. Omit to list every slot across every theme.",
      "type": "string",
      "enum": [
        "COLOR",
        "TEXT",
        "GRADIENT",
        "POSITION",
        "VECTOR",
        "SCALAR"
      ]
    },
    "theme_id": {
      "description": "Optional theme id to scope the list. Omit to list slots from all themes. Defaults to no filter; use 'Default' for the always-present built-in theme.",
      "type": "string"
    }
  },
  "additionalProperties": false
}