Regions
Get the filtered list of regions. The endpoint fully supports paging, sorting and filtering mechanism.
The tenant that the caller is acting upon.
Please note that this value is always lowercase.
^[a-z][a-z0-9]+$The page number to be retrieved where the size of the pages must be specified by the pageSize parameter. The number of the first page is 1.
1The number of documents being retrieved on the page.
60Fields to sort the response data by, following the order of the parameters from left to right.
-
Can contain multiple fields in the format:
fieldName:sortDirection, separated by commas. -
The colon with the sort direction parameter is optional.
-
Descending order is used only if the sort direction equals
descorDESC. -
Ascending order is assumed in all other cases.
While sorting by a localized field, the following rules apply:
-
If a localized field includes a language code, that language is used.
Example:name.en:ASC→ English (en) is used for sorting thenameproperty.
The language suffix takes precedence over theAccept-Languageheader. -
If a localized field does not include a language code, the
Accept-Languageheader is used.
Example:name:ASCwithAccept-Language: de→ German (de) is used for sorting. -
If a localized field has no language code and the
Accept-Languageheader contains*,
the default language from the configuration service is used.
Example:name:ASC,Accept-Language: *, default language =pl→ Polish (pl) is used. -
If a localized field has no language code and there is no
Accept-Languageheader,
the default language from the configuration service is used.
name,code:descRegion names. When specified, only regions containing the specified names will be returned.
Important: See how the Accept-Language header influences this parameter:
-
If The
Accept-Languageheader is set to*, you need to specify a language in this parameter.For example, if the
Accept-Languageheader is set to*and you want to find English names containing the word "America", this parameter should be set to "name.en=America" -
If the
Accept-Languageheader is set to a particular language or not specified, you do not need to specify a language in this parameter.For example, if the
Accept-Languageheader is set toenand you want to find names containing the word "America", this parameter should be set to "name=America"
Note: When filtering the results with this field, the contains operator is used. The operator is case-insensitive.
Region codes. When specified, only regions containing the specified codes will be returned.
Note: When filtering the results with this field, the contains operator is used.
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.
- If the header is set to a particular language or a list of languages, all localized fields are retrieved as maps with the first matched language only.
- If the header is set to
*, all localized fields are retrieved as maps of translations, where the keys are language codes and values are the fields in their respective languages. - If the header is empty, localized fields are retrieved in the default language defined in the Configuration Service.
fr-CH, fr;q=0.9, en;q=0.8, de;q=0.7In order to get information how many entities meet a filter requirements, X-Total-Count header has been introduced. The header is optional and its default value is false. It the header is provided and it is true then total count is returned in the X-Total-Count response header. In both cases (X-Total-Count true, false or not provided), the response body has the same format (array of entities). In other words, the information about total count is returned on demand, depending of an existence of X-Total-Count header in a request. Therefore, the X-Total-Count header is not returned if an API consumer didn’t ask for it.
falseThe X-Version header with value v2 is required for the endpoint.
The request was successful. A list of regions is returned.
Request was syntactically incorrect. Details will be provided in the response payload.
Internal Service Error occurred.
GET /country/{tenant}/regions HTTP/1.1
Host: api.emporix.io
Authorization: Bearer YOUR_OAUTH2_TOKEN
X-Version: text
Accept: */*
[
{
"code": "Europe",
"name": {
"en": "Europe",
"pl": "Europa"
},
"metadata": {
"createdAt": "2022-03-31T13:18:02.379Z",
"modifiedAt": "2022-03-31T13:18:02.379Z",
"version": 1
}
}
]Retrieves a region by the specified code.
The tenant that the caller is acting upon.
Please note that this value is always lowercase.
^[a-z][a-z0-9]+$The region code.
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.
- If the header is set to a particular language or a list of languages, all localized fields are retrieved as maps with the first matched language only.
- If the header is set to
*, all localized fields are retrieved as maps of translations, where the keys are language codes and values are the fields in their respective languages. - If the header is empty, localized fields are retrieved in the default language defined in the Configuration Service.
fr-CH, fr;q=0.9, en;q=0.8, de;q=0.7The X-Version header with value v2 is required for the endpoint.
The request was successful. The requested region is returned.
Request was syntactically incorrect. Details will be provided in the response payload.
The requested resource does not exist.
Internal Service Error occurred.
GET /country/{tenant}/regions/{regionCode} HTTP/1.1
Host: api.emporix.io
Authorization: Bearer YOUR_OAUTH2_TOKEN
X-Version: text
Accept: */*
{
"code": "Europe",
"name": {
"en": "Europe",
"pl": "Europa"
},
"metadata": {
"createdAt": "2022-03-31T13:18:02.379Z",
"modifiedAt": "2022-03-31T13:18:02.379Z",
"version": 1
}
}Was this helpful?

