Supported methods
List of all supported methods.| Command | Endpoints | GET | PUT | POST | DELETE |
|---|---|---|---|---|---|
| Query configured address lists | config/adress_lists | ||||
| Query configured consent groups | config/consent | ||||
| Query configured countries + ISO codes | config/countries | ||||
| Query configured shop currencies | config/currency | ||||
| Query configuration for direct orders | config/directOrder | ||||
| Query active password rules of the shop | config/password | ||||
| Query available payment methods | config/paymentMethods | ||||
| Query configured salutations | config/salutation | ||||
| Query available shipping methods | config/shippingMethods | ||||
| Query configured titles for customers | config/title | ||||
| Query the current subshop ID | subshop/current | ||||
| Query available subshops | subshop/list | ||||
| Query complete subshop URL | subshop/url |
Methods for configuration
These methods can be used to provide central shop configurations for the storefront. They deliver all selection lists and master data needed to build forms and processes, including predefined selection fields for billing and delivery addresses, countries, currencies, salutations, and titles. In addition, checkout-specific settings such as available payment and shipping methods, direct order parameters (quick entry by item number), and password rules (length restrictions, additional checks) can be read out and directly considered in the UI. Via the consent configuration, consent groups and services (e.g. captcha, tracking, media, service emails) can be viewed together with the current consent status. This allows consent dialogs, privacy settings, and the loading of external services to be controlled.GET config/addressLists
The following call returns the configured selection fields for billing and delivery addresses. It also notes which value is preselected by default. The configuration is done undergeneral.addressListElements. It can be used to build address forms (dropdowns/radio buttons including preselection) in the account, checkout, and address management.
Example call that returns all configured selection fields:
Parameter overview
| Parameter | Type | Description |
|---|---|---|
| — | — | No additional parameters. |
Example response
GET config/consent
The following call returns the consent groups defined in the shop (e.g. captcha) including the services contained in them (e.g. Google reCAPTCHA). Each group and each service has, among other things, a label, an internal identifier, a description, and the current consent status. It can be used to build the consent dialog and privacy settings, display groups/services, read current consents, and pre-fill UI switches accordingly. It can also be used to ensure that embeds/trackers are only loaded after consent. Example call that loads all consent groups defined in the shopParameter overview
| Parameter | Type | Description |
|---|---|---|
| — | — | No additional parameters. |
Example response
GET config/countries
The following call returns the countries configured in the shop including their ISO codes and display names. It can be used to populate country dropdowns (address, checkout), for validations, as well as for filtering/controlling country-specific processes. Example call that lists all countries configured in the shop:Parameter overview
| Parameter | Type | Description |
|---|---|---|
| — | — | No additional parameters. |
Example response
GET config/currency
The following call returns the currency currently configured in the shop including ISO code, ISO number, and currency symbol. It can be used for price formatting, the display in the cart/checkout, and for validations (e.g. with vouchers or shipping costs).Parameter overview
| Parameter | Type | Description |
|---|---|---|
| — | — | No additional parameters. |
Example response
GET config/directOrder
The following call returns the shop configuration for direct order (quick entry by item number). For example, it defines how many display rows are shown initially, how an item number is structured (field/separator), and what limits apply. It can be used to build the direct order form. Example call that loads the shop configuration for direct orderParameter overview
| Parameter | Type | Description |
|---|---|---|
| — | — | No additional parameters. |
Example response
GET config/password
The following call returns the active password rules of the shop (e.g. minimum/maximum length, additional checks). These rules come from the configured validation services (Validation and check services). It can be used for display and validation in password forms (registration, change/reset password) so that the entries already meet the shop requirements on the client side.Parameter overview
| Parameter | Type | Description |
|---|---|---|
| — | — | No additional parameters. |
Example response
GET config/paymentMethods
The following call returns the payment methods available in the shop as a list (each with a technical ID and display name). It can be used to populate the payment method selection in the checkout. Example call that lists all payment methods available in the shopParameter overview
| Parameter | Type | Description |
|---|---|---|
| — | — | No additional parameters. |
Example response
GET config/salutation
The following call returns the salutations configured in the shop (each with code and display text). It can be used to populate selection lists in forms. Example call that lists the salutations configured in the shop:Parameter overview
| Parameter | Type | Description |
|---|---|---|
| — | — | No additional parameters. |
Example response
GET config/shippingMethods
The following call returns all shipping methods available in the shop with technical ID, display name, and type. It can be used to populate the shipping method selection in the checkout or to display available delivery options on info pages. Example call that lists all shipping methods available in the shop:Parameter overview
| Parameter | Type | Description |
|---|---|---|
| — | — | No additional parameters. |
Example response
GET config/title
The following call returns the configured titles (e.g. academic titles) for the customer and address forms. It can be used to populate title selection lists in forms. Example call that lists all titles configured in the shopParameter overview
| Parameter | Type | Description |
|---|---|---|
| — | — | No additional parameters. |
Example response
Methods for subshop configurations
With these methods, the configuration of the subshop can be managed in the storefront context. They determine the currently active subshop ID (e.g. for language or country), list all available subshops, and generate a complete target URL for a specified subshop.GET subshop/current
The following call returns the current subshop ID to the calling storefront for reading out the active subshop for language-/country- or theme-specific contents, URLs, and configurations. Example call that returns the current subshop ID of the calling storefrontParameter overview
| Parameter | Type | Description |
|---|---|---|
| — | — | No additional parameters. |
Example response
GET subshop/list
The following call returns a list of all subshops available in the shop. It can be used to build language/country selections, to switch between subshops, or for routing/link building per subshop. Example call that returns a list of available subshops:Parameter overview
| Parameter | Type | Description |
|---|---|---|
| — | — | No additional parameters. |
Example response
GET subshop/url
The following call returns the complete shop URL for a specified subshop and optionally takes over additional parameters into the query. It can be used for language/country change or to generate links (including optional parameters). Example call that creates a link for the subshop with the ID<ID> and appends the additional parameters value1¶m and value2.
Parameter overview
Body parameters
| Parameter | Type | Description |
|---|---|---|
subshopId | string | ID of the target subshop (e.g. english) |
param[…] | string | Example: param[key1]=value1¶m[key2]=value2 |
