LIFX HTTP API

Name: LIFX HTTP API
Brand: LIFX HTTP API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTHome Automationbearer6 EndpointsREST

For Agents

Control LIFX smart bulbs and groups with state changes, toggles, and breathe effects across 6 bearer-authenticated endpoints.

Connect the LIFX HTTP API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LIFX HTTP API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with LIFX HTTP API.

Set color, brightness, and power state on a single bulb or group of LIFX lights using selector syntax

Apply different states to multiple LIFX selectors in a single batched request

Toggle LIFX lights on or off based on their current group state

Run a breathe effect that fades between two LIFX colors over a configurable cycle

GET STARTED

Start building with LIFX HTTP API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for LIFX HTTP API, keeping it validated and agent-ready. The LIFX HTTP API controls Wi-Fi-connected LIFX smart bulbs, strips, and panels using a flexible selector syntax that targets individual lights, groups, locations, or scenes. Six endpoints cover state queries, state changes, multi-selector batch updates, delta adjustments, on/off toggling, and breathe color effects. Authentication uses an LIFX personal access token issued from the cloud account portal.

Use Cases

Patterns agents use LIFX HTTP API for, with concrete tasks.

★ Smart Home Routines

Build morning, evening, and away routines that change LIFX bulb color, brightness, and power state on schedule. The /lights/{selector}/state endpoint accepts color, brightness, duration, and power in a single call so transitions feel smooth. Setup takes under an hour with a personal access token.

Set selector 'group:Bedroom' to color 'kelvin:2700' at brightness 0.4 over 30 seconds at 7am

Notification Light Cues

Use LIFX bulbs as ambient notification cues — flash red for an incident, breathe green for a build success, dim white for focus mode. The breathe effect endpoint supports two-color fades with configurable period, cycles, and persistence. Pairs with monitoring tools to surface system state in physical space.

Trigger a breathe effect on selector 'label:status' with red and white, period 2 seconds, 3 cycles

Multi-Room Scene Activation

Apply different states to multiple LIFX selectors at once with the /lights/states endpoint, enabling whole-home scenes like 'movie night' that change living-room, kitchen, and hallway lights with one request. Useful for voice-assistant integrations and scene managers.

Set selector 'group:LivingRoom' to dim warm white and selector 'group:Kitchen' to off in a single batched request

AI Agent Lighting Assistant

An AI agent uses Jentic to discover the LIFX state and breathe operations by intent and applies lighting changes in response to natural-language prompts. The agent never holds the raw token; Jentic injects credentials per execution, keeping the LIFX account isolated from the agent's prompt context.

Search Jentic for 'set LIFX bulb color', load the /lights/{selector}/state schema, and execute it for selector 'all' with color 'blue' brightness 0.5

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for lifx http api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/lights/{selector}

List lights matching a selector

PUT

/lights/{selector}/state

Set state for lights matching a selector

PUT

/lights/states

Set different states across multiple selectors

POST

/lights/{selector}/state/delta

Apply a delta adjustment to current state

POST

/lights/{selector}/toggle

Toggle lights on or off

POST

/lights/{selector}/breathe

Run a breathe color-fade effect

GET

/lights/{selector}

List lights matching a selector

PUT

/lights/{selector}/state

Set state for lights matching a selector

PUT

/lights/states

Set different states across multiple selectors

POST

/lights/{selector}/state/delta

Apply a delta adjustment to current state

POST

/lights/{selector}/toggle

Toggle lights on or off

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

LIFX bearer tokens are stored encrypted in the Jentic MAXsystem vault. The agent calls operations through scoped execution credentials — the raw token never enters the prompt or logs.

Intent-based discovery

Agents search by intent (e.g., 'turn off all my LIFX lights') and Jentic returns the matching LIFX operation across the 6 lights endpoints with the full selector and state schema.

Time to first call

Direct LIFX integration: half a day for auth and selector handling. Through Jentic: under 15 minutes — search, load, execute.

FAQs

Specific to using LIFX HTTP API through Jentic.

Why is there no official OpenAPI spec for LIFX HTTP API?

LIFX does not publish a maintained OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the LIFX HTTP API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the LIFX HTTP API use?

LIFX uses HTTP bearer authentication with a personal access token issued from the LIFX cloud account portal. Jentic stores the token in the MAXsystem vault and injects it on each request — the raw token never appears in the agent's context.

Can I control multiple LIFX bulbs in a single request?

Yes. PUT /lights/states accepts an array of selector-and-state pairs, so an agent can set different colors and brightness levels across rooms in one batched call. PUT /lights/{selector}/state can also target groups using selectors like 'group:Kitchen' or 'all'.

What are the rate limits for the LIFX HTTP API?

LIFX limits cloud requests to roughly 60 per minute per token. Sustained traffic above that returns HTTP 429. For low-latency lighting, prefer the on-LAN local protocol over the HTTP API.

How do I run a breathe effect through Jentic?

Run pip install jentic, then search Jentic with 'breathe effect on LIFX lights' to retrieve the /lights/{selector}/breathe operation. Execute it with from_color, color, period, and cycles; Jentic handles the bearer token.

Is the LIFX HTTP API free?

Yes. The LIFX HTTP API is free for owners of LIFX hardware. No subscription is required — only a personal access token tied to the LIFX account that owns the bulbs.

LIFX HTTP API

Connect the LIFX HTTP API to your agent

Capabilities

Start building with LIFX HTTP API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs