seo/urls/ endpoint provides an interface that allows you to replace the technical names of shop pages with clearer labels. You can either set these labels manually or have them generated according to a specific schema. The following sections first describe the data fields of an SEO URL and then the individual methods.
Supported methods
List of all supported methods.Data fields
Example (product)
Example (category)
Example (shop page)
Using the methods
This section describes the available endpoints for managing SEO URLs. They let you query, generate, validate, update and delete SEO URLs for categories, products and templates in the shop system. Using these methods requires the corresponding permissions to read or edit SEO data.GET seo/urls/generate/status
This endpoint is used to check the current status of SEO URL generation. It indicates whether a generation process is currently running ("running": true) or has already been completed ("running": false). This is particularly helpful when, after starting a generation process, you have to wait for its completion before proceeding.
To use this endpoint, the corresponding read permissions for SEO data are required.
Example
Response
Error codes
GET seo/urls/categories
TheGET seo/urls/categories endpoint returns a list of SEO URLs for categories.
The list can be limited using sort and filter parameters. The optional size parameter determines the number of returned results and must be in the range from 1 to 300.
To use this endpoint, the corresponding permissions to read SEO data are required.
Example
The example fetches all SEO URLs of categories that are currently used in the shop and are not just valid (main = 1) and sorts the results ascending by the resourceIdentifier field.
Response
Filter fields
createdAt, updatedAt, resourceIdentifier, path, manual, main
Sort fields
createdAt, updatedAt, resourceIdentifier, path, main
Error codes
GET seo/urls/products
This endpoint returns a list of all SEO URLs for products. Using optional parameters, the results can be filtered and sorted, for example by creation date or product ID. Thesize parameter controls the number of entries per page. It must contain a value between 1 and 300.
For access, the corresponding read permissions for SEO data are required.
Example
Response
Filter fields
createdAt, updatedAt, resourceIdentifier, path, manual, main
Sort fields
createdAt, updatedAt, resourceIdentifier, path, main
Error codes
GET seo/urls/templates
This endpoint can be used to retrieve a list of SEO URLs for general shop pages (for example login or registration). The results can be filtered and sorted using optional parameters. Thesize parameter sets the maximum number of results per page. It must contain a value between 1 and 300.
For access, the corresponding read permissions for SEO data are required.
Example
Response
Filter fields
createdAt, updatedAt, resourceIdentifier, path, manual, main
Sort fields
createdAt, updatedAt, resourceIdentifier, path, main
Error codes
POST seo/urls/check
This endpoint checks whether a specific SEO path (seoPath) is already used in the system and returns additional information about the associated resource. This can be used, for example, to avoid potential collisions before saving new URLs.
Use requires write permissions for SEO data.
Example
Request body
Response
Error codes
POST seo/urls/generate
This endpoint starts the regeneration of all SEO URLs for products and categories in the background. The response only confirms the start. GET seo/urls/generate/status shows whether the generation is still running. The optionaldeleteOld parameter determines whether all URLs that are currently not used but still valid should be deleted. Whether a URL is used in the shop or is just valid is determined by the main field.
Example
Request body
Response
Error codes
POST seo/urls/reset
This endpoint can be used to reset the SEO URL of a single page. Manually maintained URLs of this page are discarded and the URL is then recreated according to the configured schema. The new main URL can be found in themainPath field of the response.
Using the endpoint requires write permissions for SEO data.
Example
Request body
Response
Error codes
PUT seo/urls
This endpoint can be used to create a new SEO URL or update an existing one. You must specify the controller (viewControllerId) and object (resourceIdentifier) the URL is assigned to. The URL is defined by optimalPathEsc.
The shop checks manually maintained paths. Spaces, control characters and the characters ? and # are not allowed, nor are the path segments . and ... If optimalPathEsc contains such characters or segments, the shop rejects the request and does not save the path.
If the leading slash is missing from optimalPathEsc, the shop adds it automatically. The URL that is set becomes the main URL (main) of the page. The previous URLs of the page continue to lead to it, so existing links remain valid.
The endpoint requires write permissions for SEO data.
