seo/urls/ endpoint provides an interface that allows you to hide the technical names of shop pages and use clearer labels instead. They can be set manually or generated according to a schema.
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, e.g. by creation date or product ID. Thesize parameter controls the number of entries per page and must be in the range 1–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 retrieves a list of SEO URLs for general shop pages (e.g. login, registration). The results can be filtered and sorted using optional parameters. Thesize parameter sets the maximum number of results per page and must be in the range from 1 to 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
URLs are regenerated. The optionaldeleteOld parameter determines whether all URLs that are currently not used but still valid are deleted. Whether a URL is used in the shop and not just valid is determined by the main field.
Example
Request body
Response
Error codes
POST seo/urls/reset
This endpoint starts the (re)generation of an SEO URL. The old value is not deleted. 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 endpoint requires write permissions for SEO data.
