Changelog
Dated changes to the Luma Agents /v1 API that you can see as a caller — new fields, new status codes and changed behavior — newest first.
Changes to the /v1 API that you can see as a caller, newest first. Dates are in UTC. Breaking changes are announced here before they ship.
Every response carries an X-API-Version header (currently 2026-04-01). It reports the version that answered; you cannot send it to choose a version.
2026-11-09
Section titled “2026-11-09”GET /v1/usageresponses addperiod_source, which says where the reported window came from:subscription(your current billing period),calendar_month(the current UTC month) orexplicit(thestartandendyou sent). See Usage and credits.
2026-11-04
Section titled “2026-11-04”- Failed
POST /v1/generationsrequests answer by cause. Some errors now carry anerrorobject with a machine-readablecodeand aretryflag next todetail. See Error handling.- An input refused when the generation is dispatched answers
422withUSER.ARTIFACT.MODERATED(rejected by moderation) orUSER.INPUT.INVALID_PROMPT(missing, deleted or failed), instead of500. - A transient failure, such as a timeout, answers a retryable
503withTRANSIENT.SERVICE.UNAVAILABLE. - A
500withINTERNAL.SYSTEM.DATABASE_ERRORmeans the generation may still run. Do not resubmit it.
- An input refused when the generation is dispatched answers
2026-11-03
Section titled “2026-11-03”- Generation responses (
POST /v1/generationsandGET /v1/generations/{id}) carry ausageobject. While usage reporting is off it isnull; once it is on,usage.credits_chargedis the credits charged for the generation after billing settles.
2026-10-27
Section titled “2026-10-27”POST /v1/generationsacceptsexpires_at, a deadline after which the generation is deleted. It needs the managed retention add-on and is ignored without it. See Generation deletion.
2026-10-26
Section titled “2026-10-26”- A malformed id in a
/v1URL, such asGET /v1/files/not-a-uuid, answers404, the same as a well-formed id that does not exist. It used to answer422.
2026-10-24
Section titled “2026-10-24”GET /v1/creditsno longer returnsbalance_usd_cents, which was alwaysnull. Readbalance_credits. See Usage and credits.
2026-10-23
Section titled “2026-10-23”- The API Reference documents
DELETE /v1/generations/{id}andGET /v1/deletions/{task_id}for clients with deletion enabled. They are HTTP only; the SDKs and CLI do not wrap them yet.
2026-10-19
Section titled “2026-10-19”POST /v1/generationsrefuses a layering request that namesuni-1-maxwith422(layering is only available on uni-1). It used to run asuni-1.GET /v1/generations/{id}reports a layering generation asprocessingonce layering starts, instead ofqueueduntil it completes.
2026-10-15
Section titled “2026-10-15”POST /v1/generationsanswers a retryable503when registering the request’s reference images fails briefly, instead of500.