Skip to content
Lumean API
DELETE/templates/{template}

Delete Template

Deletes the key owner's template. Irreversible, with no confirmation step: the template disappears from GET /templates and GET /templates/browse, requests to /templates/{template} return 404, and a new order or chunk preview with that template_id returns 422, exactly as for a template that never existed.

templates.write

Orders already created from it, and their results, stay untouched and keep running with the settings they had at creation time (orders created before late September 2026 have no snapshot and keep running with the template configuration as of its deletion). If such orders exist, the template is kept hidden: GET /orders/{order} still shows it in the template field — with that order's config.

Required key permission: templates.write.

On this page(3)

Parameters

The inputs live inside the request line: fill in a value and you get a ready URL. Below are the type, whether it is required and the allowed values of every parameter.

DELETEhttps://api.lumean.app/api/public/templates/
  • stringin pathrequireduuid

    Template UUID — 36 characters, not a number.

    Take it from the id field: POST /templates returns it on creation, and GET /templates and GET /templates/browse list it.

    The value goes straight into the request line above.

Possible responses

200

Success. The payload is in data.

Body example
{
  "success": true,
  "message": "Template deleted",
  "data": null
}
Response fields
successrequired

Success flag. Branch on the HTTP status code instead: any 2xx response carries true here, while an error comes back in a different shape that need not contain this field at all.

boolean
messagerequired

A human-readable note in the account language. Fine to show to a user; do not parse it — the wording changes without notice and is not an error code.

string
datarequired

Always null: there is nothing left to return. The 200 status is the confirmation.

nullable
null
401

The key is missing, unknown, disabled or expired.

Analyse this response
Body example
{
  "success": false,
  "message": "API key is missing. Provide it in the X-API-KEY header.",
  "data": null
}
Response fields
successrequired

Always false in error responses.

boolean
messagerequired

Error text in the key's language (set through the X-Locale header).

string
datarequired

Always null when the request is rejected before processing.

nullable
null
403

The key lacks the required permission, or the object belongs to another user.

Analyse this response
Body example
{
  "success": false,
  "message": "This API key does not have permission to perform this action."
}
Response fields
messagerequired

Error overview.

string
404

Not found, or not reachable with this key.

Analyse this response
Body example
{
  "success": false,
  "message": "Resource not found."
}
Response fields
successrequired

Always false in error responses.

boolean
messagerequired

Error text in the key's language (set through the X-Locale header).

string
reasonoptional

Machine-readable reason — present on business refusals (for example, invalid_order_status); other errors omit it. Branch on it, not on the message text.

string
error_codeoptional

The same machine-readable code as in reason — a second name for the field. Arrives together with reason; the values always match.

string

Nearby

Neighbouring operations

Feed this page to an AI

Open .mdllm.md

spec 0.0.1