The Passport sizes data includes a mix of lowest "research" levels and pre-calculated aggregated levels. This allows you to pick on any particular categories you are interested in. There is a potential risk though if you are taking data outside of Passport and performing your own manipulations, that you could miscalculate by double-counting data. For example, this is a very small part of the Packaged Food product hierarchy:

• Packaged Food
  • Confectionery
    • Chocolate Confectionery
    • Gum
      • Bubble Gum
      • Chewing Gum
    • Sugar Confectionery

In the example above, data on Passport for Gum is pre-calculated to be the sum of Chewing Gum + Bubble Gum, whereas total Confectionery is the sum of Chocolate Confectionery, Sugar Confectionery, and Gum. If you pull this data from Euromonitor's stats API and introduce it into some BI tools you might end up accidentally adding together Chewing Gum plus Bubble Gum plus total Gum - ie double-counting Gum. If your intention is to pull out all the data on Passport without further manipulation, then it makes sense to pull all the rows available. If you are planning to recombine data from the lowest levels then it's better to pull only data for those lowest levels - and it’s important to know what is the lowest level on all countries.

That is where the Data Slices endpoints come to help you. A "Data Slice" in the Euromonitor API is a subset of products, combined with information about the relative product hierarchy. There are two main data slices on most industries:

1. All products
2. Lowest level products

In addition to these data slices 1 and 2, some industries have additional data slices which provide alternative paths through which to aggregate lowest level data.

This endpoint allows you to query the names of the data slices available for a specific industry, so you can use these data slice IDs to refine a request to either the Data Slice Category endpoint or to the Market Sizes endpoint.

URI	https://api.euromonitor.com/catalog/dataslices
Supported verbs	GET, POST
Required headers	Ocp-Apim-Subscription-Key, Accept, Authorization
Supported formats	JSON, XML, CSV
Parameters
IndustryCodes	An array of Industry Codes, as retrieved from the Category catalog

A sample GET request might look like this:

GET https://api.euromonitor.com/catalog/dataslices?IndustryCodes=CT HTTP/1.1
	Host: api.euromonitor.com
	Authorization: Bearer <tokenstring>
	Accept: application/json; api-version=1.0
	Ocp-Apim-Subscription-Key: 173bad6f0b319h23add9ad162493915e

The POST version of the same request will look like this:

POST https://api.euromonitor.com/catalog/dataslices HTTP/1.1
	Host: api.euromonitor.com
	Authorization: Bearer <tokenstring>
	Accept: application/json; api-version=1.0
	Content-Type: application/json
	Ocp-Apim-Subscription-Key: 173bad6f0b319h23add9ad162493915e

	{
		"industryCodes": [
			"CT"
		]
	}

A successful response body will have the following structure in JSON format:

[
		{
			"Id": 0,
			"Name": "string",
			"IndustryCode": "string",
			"IndustryName": "string"
		}
	]

It is an array of DataSlice objects, each with the following members:

DataSliceid	The ID of the data slice
DataSliceName	The name of the data slice
IndustryCode	The industry code
IndustryName	The name of the industry