Skip to content
Lumean API

service_not_found — no such service

422service_not_foundno Retry-After

What happened

422 with reason: "service_not_found" and without errors: the request passed shape validation but failed at service resolution. The order was not created.

Why

The most common cause is a task_type that cannot be created publicly. The values image, txt2img, remix, image_edit, voice_clone are in the enum, so they pass request validation — but no service with that code exists in the public API. Only tts, sfx, music, and voice_search can be created with an API key; the other enum values exist solely for the GET /orders?task_type[]=… filter. The second cause: the service exists but is not active.

What to do right now

Check against the list of creatable types and do not send the rest. The same reason appears on GET /usage/{service} as a 404: there, service is the service_code from GET /usage, not an arbitrary string.

Which request to send next

POST /orders with a task_type from the four supported ones or with a template_id (for TTS a template is required: the voice is set by config.tts_settings.voice_id of the template, and there is no orders.voice_id field). Which config keys the service accepts — GET /templates/config-options?service=<code>.

Feed this page to an AI

Open .mdllm.md

spec 0.0.1