Prices
Was this helpful?
Was this helpful?
Price's unique identifier, generated when the price is created.
Your Emporix tenant's name.
Note: The tenant should always be written in lowercase.
^[a-z][a-z0-9]+$If set to true, the response will also include the price model's details.
falseList of language codes acceptable for the response. You can specify factors that indicate which language should be retrieved if the one with a higher factor was not found in the localized fields.
*, all localized fields are retrieved as maps of translations, where the keys are language codes and values are the fields in their respective languages.Price's unique identifier, generated when the price is created.
Your Emporix tenant's name.
Note: The tenant should always be written in lowercase.
^[a-z][a-z0-9]+$No content
Your Emporix tenant's name.
Note: The tenant should always be written in lowercase.
^[a-z][a-z0-9]+$Codes of sites for which prices should be retrieved.
mainCodes of currencies in which prices should be retrieved.
Date on which retrieved prices should be valid, compliant with the ISO 8601 standard. Format:date-fullyear "-" date-month "-" date-mday "T" partial-time time-offset
2022-01-01T00:00:00ZList of properties used to sort the results, separated by colons. The order of properties indicates their priority in sorting.
Possible values:
{fieldName}{fieldName}:asc{fieldName}:descNote: If you want to sort the results by localized properties, the possible values are:
{fieldName}.{language}{fieldName}.{language}:asc{fieldName}.{language}:descIf the sorting direction is not specified, the fields are sorted in ascending order.
Page number to be retrieved. The number of the first page is 1.
Note: If the pageNumber parameter is passed, size of the pages must be specified in the pageSize parameter.
1Number of items to be retrieved per page.
60IDs of customers for whom the retrieved prices should be valid.
Note: This parameter is only available in the v2 version of the Price Service.
ID of the price model to which the retrieved prices should be assigned.
Note: This parameter is only available in the v2 version of the Price Service.
IDs of products for which prices should be retrieved.
Note: This parameter is only available in the v2 version of the Price Service.
Item types for which prices should be retrieved. Possible values:
PRODUCT
SKU
Note: The SKU value is a preview value - the system does not fully operate on the SKU concept yet.
Note: This parameter is only available in the v2 version of the Price Service.
Codes of countries for which prices should be retrieved.
Note: This parameter is only available in the v2 version of the Price Service.
A product or SKU name. This attribute is available only for Price v2
List of language codes acceptable for the response. You can specify factors that indicate which language should be retrieved if the one with a higher factor was not found in the localized fields.
*, all localized fields are retrieved as maps of translations, where the keys are language codes and values are the fields in their respective languages.Your Emporix tenant's name.
Note: The tenant should always be written in lowercase.
^[a-z][a-z0-9]+$List of languages in which localized fields in the request body are provided.
Content-Language header is set to *, the localized fields should be provided as maps of translations, where the keys are language codes and values are the fields in their respective languages.Content-Language header is set to a specific language, the localized fields should be provided as strings.Content-Language header is empty, the endpoint will asume that the localized fields are provided in the default language defined in the Configuration Service.Note: You can provide the localized fields only in languages defined in the Configuration Service. In case the fields are provided in languages that are not defined in the Configuration Service, the request will be rejected.
Custom price identifier. If not provided, it is automatically generated.
Product's uniform resource name.
Currency code, compliant with the ISO 4217 standard.
[A-Z]{3}ID of the price model to which the price should assigned. If the ID is not provided, the default price model is used.
Your Emporix tenant's name.
Note: The tenant should always be written in lowercase.
^[a-z][a-z0-9]+$List of languages in which localized fields in the request body are provided.
Content-Language header is set to *, the localized fields should be provided as maps of translations, where the keys are language codes and values are the fields in their respective languages.Content-Language header is set to a specific language, the localized fields should be provided as strings.Content-Language header is empty, the endpoint will asume that the localized fields are provided in the default language defined in the Configuration Service.Note: You can provide the localized fields only in languages defined in the Configuration Service. In case the fields are provided in languages that are not defined in the Configuration Service, the request will be rejected.
Custom price identifier. If not provided, it is automatically generated.
Product's uniform resource name.
Currency code, compliant with the ISO 4217 standard.
[A-Z]{3}ID of the price model to which the price should assigned. If the ID is not provided, the default price model is used.
Your Emporix tenant's name.
Note: The tenant should always be written in lowercase.
^[a-z][a-z0-9]+$List of languages in which localized fields in the request body are provided.
Content-Language header is set to *, the localized fields should be provided as maps of translations, where the keys are language codes and values are the fields in their respective languages.Content-Language header is set to a specific language, the localized fields should be provided as strings.Content-Language header is empty, the endpoint will asume that the localized fields are provided in the default language defined in the Configuration Service.Note: You can provide the localized fields only in languages defined in the Configuration Service. In case the fields are provided in languages that are not defined in the Configuration Service, the request will be rejected.
Price's unique identifier, generated when the price is created.
Your Emporix tenant's name.
Note: The tenant should always be written in lowercase.
^[a-z][a-z0-9]+$| Value | Description |
|---|---|
true |
A partial update will be performed. |
false |
A full product replacement will be performed. |
List of languages in which localized fields in the request body are provided.
Content-Language header is set to *, the localized fields should be provided as maps of translations, where the keys are language codes and values are the fields in their respective languages.Content-Language header is set to a specific language, the localized fields should be provided as strings.Content-Language header is empty, the endpoint will asume that the localized fields are provided in the default language defined in the Configuration Service.Note: You can provide the localized fields only in languages defined in the Configuration Service. In case the fields are provided in languages that are not defined in the Configuration Service, the request will be rejected.
Your Emporix tenant's name.
Note: The tenant should always be written in lowercase.
^[a-z][a-z0-9]+$Fields that should be expanded with additional information in the response body. Expressed as strings separated by commas.
Possible values:
priceModelList of item IDs for which the prices should be retrieved.
Currency in which the prices should be retrieved, as defined in the Currency Service.
[A-Z]{3}Code of the site for which the prices should be retrieved.
IDs of customers for whom the retrieved prices should be valid.
Date on which retrieved prices should be valid, compliant with the ISO 8601 standard.
Format:
date-fullyear "-" date-month "-" date-mday "T" partial-time time-offset
Flag indicating whether the prices should be retrieved as net or a gross values.
If no price that matches the criteria is found for the specified site, the price searching functionality will try to find the best price for the main site. To enable this option, this field needs to be set to true.
Note: Using the fallback mechanism may impact the performance as the price searching has to run a second time. If the fallback mechanism is used, the response's siteCode field will be set to main.
falseSearch mode indicating which prices should be taken into account regarding their principal-related restrictions.
Possible values:
ALL_PRICES - all prices should be taken into account regardless of their principal restrictions.COMMON_PRICES - only the prices with no principal restrictions should be taken into account.USER_SPECIFIC_PRICES - only the prices applicable for a given principalId should be taken into account.ALL_PRICESPossible values: