datafeeds/ endpoint allows you to manage your data feeds. With this interface, you can update and delete already created feeds or create new data feeds.
Supported methods
List of all supported methods.Data fields of a data feed
Example
Data feed templates
Example
Methods for data feeds
This section describes all endpoints for managing data feeds in the shop system. The interface can be used to create, retrieve, update, delete, and schedule exports of data feeds.GET datafeeds
This method returns a paginated list of all data feeds present in the system.By default, 100 entries are returned per request. The optional
size parameter can be used to adjust the number of returned records — up to a maximum value of 300. The size value can be freely chosen between 1 and 300.The result list can be specifically restricted and ordered via defined filter and sort parameters. Read permissions for data feeds are required to access.
Example
Response
Filter fields
id, active, name, fileName, templateId, subshopIds, targetDirectory, exportStatus, lastExportStarted, lastExportFinished, createdAt, updatedAt
Sort fields
id, active, name, fileName, templateId, subshopIds, exportStatus, lastExportStarted, lastExportFinished, createdAt, updatedAt
Error codes
GET datafeeds/{id}
This method retrieves the complete details of a single data feed by its unique ID. The endpoint returns all configured properties of the data feed, including name, export options, directory information, and status information. Access requires the appropriate read permission for data feeds.Example
Response
Error codes
PUT datafeeds/{id}
This method updates an existing data feed by its unique ID. Data remains unchanged until generation. In the request body, various properties of the data feed can be changed, including name, status, file name, export options, and target directories. The fieldscreatedAt, updatedAt, lastExportStarted, lastExportFinished, and exportStatus can be passed, but are ignored by the system and not overwritten.
The updated data feed is returned as a JSON object in the response.
Write permissions are required for execution.
Example
Request body
Response
Error codes
POST datafeeds
This method creates a new data feed. The properties of the data feed, such as name, status, file name, export options, and target directories, are defined via the request body. The fieldscreatedAt, updatedAt, lastExportStarted, lastExportFinished, and exportStatus can be passed but are ignored by the system and set automatically.
After successful creation, the complete data feed is returned as a JSON object.
Execution requires create permissions.
Example
Request body
Response
Error codes
DELETE datafeeds/{id}
This method permanently deletes an existing data feed by its unique ID. Access to this endpoint requires delete permissions.Example
Response
Error codes
Methods for data feed templates
This section describes the endpoints for managing templates for data feeds. Templates define the structure and the fields contained in a data feed, such as product data, category data, or further information. Before creating a data feed, a suitable template must be created, since this forms the basis for the later export.GET datafeeds/templates
This method returns a paginated list of all data feed templates present in the system. The result list can be restricted and sorted via filter and sort parameters. The templates form the basis for later data feed creation. Access to this endpoint requires read permissions for data feeds.Example
Response
Filter fields
id, name, content, createdAt, updatedAt
Sort fields
id, name, content, createdAt, updatedAt
Error codes
GET datafeeds/templates/{id}
This method retrieves the complete details of a single data feed template by its unique ID. The response contains the master data of the template and its content definition. Access to this endpoint requires read permissions for data feeds.Example
Response
Error codes
PUT datafeeds/templates/{id}
This method updates an existing data feed template by its unique ID. In the request body, the name and the content (content) of the template can be changed. The fields createdAt and updatedAt can be passed, but are automatically managed by the system and not overwritten.
After successful update, the complete template is returned in the response. Write permissions are required.
Example
Request body
Response
Error codes
POST datafeeds/templates
This method creates a new data feed template in the system. In the request body, the name of the template and its content (content) must be provided. The fields createdAt and updatedAt can be passed, but are automatically set by the system and not accepted.
After successful creation, the complete template with all related information is returned as a JSON object.
Create permissions are required.
Example
Request body
Response
Error codes
POST datafeeds/templates/validate
This method checks whether the provided content (content) of a data feed template is syntactically correct.
Possible formatting errors or invalidities are detected before a template is saved or used. The request body must contain the content field as a string. The validation does not save any data; it serves exclusively for the check.
Read permissions for data feeds are required.
Example
Request body
Response
Error codes
DELETE datafeeds/templates/{id}
This method deletes an existing data feed template by its unique ID. The successful deletion is confirmed by the JSON object{"success": true} and the status code. A template can only be deleted if it is no longer in use.
Delete permissions are required for access to this endpoint.
Example
Response
Error codes
Methods for building data feeds
This section describes all endpoints that control the build process of data feeds. The interface can be used to start build processes for individual or all data feeds, query the status of a running build, and prepare time- or import-controlled builds. The build processes ensure that current and complete export files are generated on the basis of the existing templates and data.GET datafeeds/build/{id}/status
This method returns the current status of the build process of a data feed. It enables you to monitor whether a data feed is currently being created, has already been completed, or whether errors occurred during creation. Each element of the response containsfilePath (relative file path) and status (status information). Additionally, the url field is returned if the data feed’s saveTarget is "contentData".
Read permissions for data feeds are required for access.
Example
Response
Error codes
POST datafeeds/build/all
This method starts the build process for all data feeds present in the system. All defined data feeds are recreated. Execution is asynchronous; the endpoint only confirms the start of the process. Publish permissions for data feeds are required.Example
Request body
Response
Error codes
POST datafeeds/build/{id}
This method starts the build process for a specific data feed by its unique ID. The selected feed is recreated. Execution is asynchronous; the endpoint only confirms the start of the build process. With the optional query parametersubshopId (can be specified multiple times), the build can be restricted to specific subshops.
Publish permissions for data feeds are required.
Example
Request body
Response
Error codes
POST datafeeds/build/hour/{hour}
This method starts the generation of data feeds that must be generated at a specific hour. The path parameter{hour} specifies the hour in 24-hour format (0 to 23). Generation is asynchronous — this means the response does not return a finished file but only confirms the start of the process.
Publish permissions for data feeds are required.
