/images/ provides comprehensive functions for managing images of various formats in our shop system.
Through various endpoints, you can upload, convert, and delete images as well as retrieve the corresponding URLs.
Supported methods
List of all supported methods.Supported image formats
BitmapFITSGIFGraphics Kernel SystemJPEGNIFFPMPNGXFIGXPMTIFFGIMP XCFwebpAVIF
Data fields of a directory
Example
Methods for managing images
GET images/url/{typeId}
GET images/url/{typeId}
This endpoint returns the URL of an image based on the specified type (typeId) and, optionally, the desired format.
It is used to determine the storage location of an image in the system — particularly when the path is not known after upload.Valid values for
typeId are:
categoriesfor category images,productsfor product images,appImagesfor images within the app interface.
Example
Response
GET images/directories/{typeId}
GET images/directories/{typeId}
This endpoint returns the structure of the available image directories as a tree structure. Depending on the value of thetypeId parameter, either source directories (source) or target directories (target) are returned. The response contains a hierarchical representation of the existing folders and subfolders.
Example
Response
Error codes
GET images/convert/results
This endpoint returns a paginated list of the results of completed image conversions. For each converted image, information such as source file, target file, target format, file size, conversion duration, and processing status is returned. This makes it possible to track whether and how an image has been successfully converted to various formats.Query parameters
Example
Response
Error codes
GET images/convert/status
This endpoint returns the current status of a running image conversion process, or the last known status of a completed one. It returns information such as progress, the number of successful or failed conversions, and timer data (start time, end time, duration). The endpoint allows monitoring and evaluation of image conversion processes in the system.Example
Response
Error codes
GET images/report/products
This endpoint returns a report on the use of product images in the shop system. It lists both missing images (missingImages) and unused images (unusedImages). The report helps identify image files that are no longer assigned to an active product or that are missing in the system, and thus supports the optimization of image data management.
Example
Response
Error codes
POST images/upload
This endpoint enables uploading an image to the shop system. The image is transmitted as a Base64-encoded string in the request body. Additionally, it can be specified which formats the image should be converted to. After a successful upload, the path to the stored image file is returned.Example
Request body
Response
Error codes
POST images/upload/convert
This endpoint enables uploading an image with immediate subsequent conversion to one or more defined target formats. The image is transmitted as a Base64-encoded string in the request body. In contrast to the regular upload, the conversion is automatically triggered here, so that optimized or format-adapted variants can be created directly. After completion, an overview of the generated image files is returned.Example
Request body
Response
Error codes
POST images/report
This endpoint starts the check for missing or unused image files in the system. Execution is asynchronous: no direct result is returned after a successful start of the check. The complete report can then be retrieved viaGET /images/report/. The endpoint ensures that image data can be regularly checked for consistency.
Example
Request body
Response
Error codes
POST images/convert/start
This endpoint starts the conversion process for images stored in the system. The images are converted into the respectively defined target formats (e.g. different sizes or file formats). Execution is asynchronous, but a direct response about the converted images is provided after the process is started. The progress and status of the conversion can be queried later via the endpointGET /images/convert/status.
Example
Request body
Response
Error codes
POST images/convert/cancel
This endpoint cancels a currently running image conversion process. Cancellation is not asynchronous; a direct response on the converted images is provided immediately. After execution, the status of the conversion process can be queried again via the endpointGET /images/convert/status. The cancellation operation requires appropriate permissions.
Example
Request body
Response
Error codes
POST images/directories/{typeId}
POST images/directories/{typeId}
Creates a directory. FortypeId = source, these are source directories; for typeId = target, these are target directories.
Example
Request body
Response
Error codes
DELETE images/directories/{typeId}
DELETE images/directories/{typeId}
This endpoint deletes a directory within the specified area (source or target) for image files.
The path to the parent directory and the name of the folder to be deleted can be defined via the request body. After successful deletion, the updated directory structure without the deleted directory is returned as a tree structure.
Example
Request body
Response
Error codes
DELETE images/upload/{typeId}
DELETE images/upload/{typeId}
This endpoint deletes one or more images within a specified area (categories, products, or appImages).
The name of the file(s) to be deleted is provided via the fileName field in the request body, either as a string or as an array of strings. Optionally, the formats field can be used to specify which image formats should be considered; otherwise all formats are deleted. The endpoint carefully checks the validity of the provided parameters and handles both single and multiple deletions.
Example
Request body
Response
Error codes
DELETE images/upload/{typeId}/{filename}
DELETE images/upload/{typeId}/{filename}
This endpoint deletes a specific image within a specified area (categories, products, or appImages).
The file name to be deleted is passed directly as a path parameter (filename). Additionally, further file names (fileName) can be specified in the request body, either as a single string or as an array of strings.
The optional formats field can be used to specify which image formats should be deleted; otherwise all formats are considered. The endpoint supports both single image deletion and combined deletion of multiple images.
