Responses and errors

Success responses · HTTP responses and errors · Job statuses · Job errors · Cancellation results

The HTTP status describes the request result; status in the response body describes the Job execution. A Job can be failed or canceled even when the HTTP status is 200.

Success responses

202 Accepted means the Job was accepted, not completed. 200 OK means the lookup or cancellation request was processed. Check the Job's status or the cancellation's results[].status as well. Success responses have no common top-level code field.

HTTP responses and errors

Nordy request errors contain top-level code, message, and requestId fields. Include requestId when contacting support. The same code can have different meanings depending on the HTTP status and API.

{
  "statusCode": 400,
  "code": "INVALID_INPUT",
  "message": "The request is invalid.",
  "requestId": "request-id",
  "details": {
    "field": "prompt"
  }
}

This table collects the response definitions from each API reference. — means no common error code is defined for that response. 304 is not an error and has no response body. Other node info responses may use status codes and bodies returned by ComfyUI.

Job statuses

Used in status for create and get responses, and jobs[].status for list responses.

Job errors

Returned in the Job's error.code, separately from request error codes. For list responses, check jobs[].error.code. The error field is null unless the Job is failed or canceled.

Cancellation results

Cancel Jobs can return different results per ID with HTTP 200. Check results[].status. Cancel all Jobs returns only canceled_count.

Preserve unknown error codes too. If a create request times out or loses its response, read Retries and timeouts before submitting again.