When an API call fails, the system returns an HTTP error code — e.g. 400, 401, or 500 — along with an <error_info> XML package describing the issue. This helps client applications diagnose and handle errors correctly.
Code | Meaning | HTTP Status | Notes |
100 | Internal Error | 500 | Unknown server-side exception. See <details>. |
101 | Input Error | 400 | Missing or malformed request parameters. |
102 | Recipe Error | 500 | XML serialization/deserialization failure. |
103 | Design Format Error | 400 | Unsupported input or output file format. |
110 | Authentication Fail | 401 | Invalid App ID or App Key. |
111 | Authentication Error | 401 | Exception during authentication process. |
| 120 | CAD Server Error | 500 | Internal error in CAD server. See cadcode |
If the error is related to the CAD server, the cadcode attribute will be present to provide more specific insight.
cadcode | Error | Meaning |
0x22100011 | ERROR_INCORRECT_XML_DATA_STRUCTURE | Invalid XML structure in input. |
0x20000100 | ERROR_INVALID_VERSION | Unsupported or unknown recipe version. |
0x20000104 | ERROR_FILEVERSION_TO_GREAT | File created with a newer, unsupported software version. |
0x20000106 | ERROR_FILE_VERSION_OBSOLETE | File created with an outdated, unsupported software version. |
0x22100010 | ERROR_NOT_A_SINGLE_LETTERING_DESIGN | Missing required lettering content in recipe. |
0x54F | ERROR_INTERNAL_ERROR | Generic internal failure. |
0x22100001 | ERROR_BAD_PTR | Internal pointer/reference error. |
0x1E | ERROR_READ_FAULT | File format doesn't match expected type. Often from non-standard tools. |
0x21000014 | ERROR_INVALID_DESIGN_EXTENTS_STITCH | Design exceeds the stitching area. |
| 0x21000018 | ERROR_INVALID_HOOP_FOR_MACHINE_MODEL | Hoop unsupported on the selected machine. |
0x21000032 | ERROR_COLOR_SECTION_TOO_BIG | Stitch count too high in one color section. |
0x21000033 | ERROR_DESIGN_EXCEEDS_MACHINE_STITCH_AREA | Design exceeds the target machine’s max area. |