Error information

Error information

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.


XML structure

Standard API-level error

<error_info
errorcode="111" <!-- API error code --> message="Exception occurs when logging in 3scale." <!-- Short error description --> > <details> <!-- Detailed diagnostic info --> CS_threescale.ApiException: application_not_found : application with id="46329c141" was not found at CS_threescale.Api.aux_authorize(Int32 key_type, String id, String key) ... </details>
</error_info>

Error with CAD server code

<error_info errorcode="120" <!-- API error code --> message="Exception occurs inside CAD Server." <!-- Short error description --> cadcode="0x1E" <!-- CAD server error code --> > <details> <!-- Diagnostic details from CAD server --> Wilcom.Servers.CADEmbServer.CADException: Call to EmbServer_GetDesignInfo failed. Return code: ERROR_READ_FAULT ... </details> </error_info>

Usage

The <error_info> XML can be returned by any API method when an error occurs. HTTP response will include:
  1. A non-200 status code — 400, 401, 500, etc.
  2. A corresponding <error_info> XML payload in the body. This element applies to all API methods.
  3. The errorcode helps determine the category of failure.
  4. The message is a summary for display or logging.
  5. The <details> element may contain stack traces or diagnostics for troubleshooting.
  6. If cadcode is present, refer to CAD server-specific errors for more precise diagnosis.
  7. The information helps developers identify problems and take corrective actions, whether on the client side or when reporting issues to Wilcom support.
Info
Always check both the HTTP status code and the contents of error_info to handle errors gracefully.

Elements

Element
Details
error_info
Root element for all error responses.
errorcode (integer)
Indicates the type of error encountered. See API Error Codes and CAD Error Codes below.
message (string)
A short, human-readable description of the error.
cadcode (hex string, optional)
CAD-specific error code. Only included when errorcode = 120.
<details> (optional)
Contains stack traces or debugging information helpful for development or support.

API error codes

When is error_info returned?
  1. Any API method may return error_info when a request fails.
  2. The HTTP status code will indicate the general error category — 400, 401, 500, etc — while error_info gives specific details.
API error codes include:
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

CAD error codes

If the error is related to the CAD server, the cadcode attribute will be present to provide more specific insight.

Example:

<error_info
errorcode="120" message="Exception occurs inside CAD Server." cadcode="0x1E" > <details> Wilcom.Servers.CADEmbServer.CADException: Call to EmbServer_GetDesignInfo failed. Return code: ERROR_READ_FAULT ... </details> </error_info>

Common CAD error codes:

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.
    • Related Articles

    • Feature Transfer Error (Error - 1644)

      Issue ERROR - 1644 during Embroidery Studo 2026 software installation Cause Sometimes the "policy" is simply a lack of elevated permissions. Required Information from you From the affected PC, send the following details to the Support team. 1. ...
    • If Embroidery Studio software crashes or shows a System Error too often, please send an Issue Report

      IMPORTANT: Please make sure you quoted the Dongle tag number in the issue report form, so we can find your user account and the details of your ES e4/ ES DE HL software in our system. With ES 2026/ES 2025/ES DE/ES DE HL/ES e4, we implemented a new ...
    • Error SFTP Operation Failed. ComponentActivator could not instantiate EClib.Model.SFTP.DeviceUnmountTransaction

      Error Message - Error SFTP Operation Failed. ComponentActivator could not instantiate EClib.Model.SFTP.DeviceUnmountTransaction Solution: Update your EmbroideryStudio e4.5 and ensure that the EmbroideryConnect device has the latest Firmware running ...
    • View design information

      The Design Information pane displays detailed information about a selected design in the Library. From this pane you can review metadata, inspect technical design properties, view available colorways, and manage attachments associated with the ...
    • Update design information

      The update design information feature allows you to modify the metadata associated with a design in Wilcom Library. Keeping design information up to date ensures designs are easy to find, correctly categorized, and ready for production workflows. ...