Overview

The amount of data to be output from exports and the API is the same for each data format and output format combination.Whichever output format is selected, the content of the data in the data format is always identical.

However, there is a contract-dependent limit per export for all combinations of data format and output format.

The following formatting types are permitted and use the specified format identifiers. The xsd schema of the available output formats, via the info method to retrieve.

Data format /
output format
csv json xml scope of application
standard * x x x Products and Product
standardUpdate x x x Products and Product
developer ** x x x Products and Product
developerUpdate x x x Products and Product
deal   x x Orders
quote   x x offers
company   x x Manufacturers and suppliers
producttype   x x categories
ORDER, ORDERRESPONSE,
DISPATCHNOTIFICATION, INVOICE
    x OpenTrans 2.1 Order documents
QUOTE     x OpenTrans 2.1 Offer Documents

* Recommended by Itscope, covering almost all applications.

** only for professionals who are familiar with the ITscope data structure. Is recommended only with a technical consultation through ITscope.

 

 

Data formats for article installations

default

This profile is recommended to cover almost all ITscope connections. This type contains only selected data that is designed to be sufficient for most purposes without generating too much data volume. The data in the profile is aggregated, ie everything is already required for immediate use. Ids, pictures, texts, keys, prices, technical features.

This profile provides the data in simply usable form - as flat CSV files, or in XML, or in JSON format with product, vendor, feature and cross-selling data.

This profile is recommended for daily matching.

 

developer

All data available in the ITscope platform for a product are output, including complete content. This profile is really only for professionals, users who are familiar with the complete structure of the ITscope data and are willing to learn it.

We always recommend you to consult ITscope for technical advice. Through an appropriate introduction to the data structure and importance of the respective data objects directly to your needs, unnecessary effort is saved.

Tabular formats are available as a single table for this data type. For relevant 1: 1 relationships, the referenced record was included in the table. For each 1: n relationship, a number of the references that are to be included are defined. The same number of fields are always used in the total table. If there are only three configured four references, the field entries are generated for all four, but remain empty for the missing fourth set. For repetitive fields, the field names are numbered with a counter.

This profile is recommended for daily matching.

Data formats for item updates

standardUpdate

The update profile always matches its main profile and provides only motion data for updating, such as prices, stocks, delivery dates. The data volume is less than the main profile and is mostly used to keep the target system's motion data up-to-date.

This profile can be used for an efficient hourly comparison of prices and availabilities.

developerUpdate

The update profile always matches its main profile and provides only motion data for updating, such as prices, stocks, delivery dates. The data volume is less than the main profile and is mostly used to keep the target system's motion data up-to-date.

This profile can be used for an efficient hourly comparison of prices and availabilities.

 

Output format properties

The data output from exports and the API can be written in the following formats.

  • Tabel format: CSV
  • Hierarchical format: XML, JSON

General properties for all output formats

 

  • No carriage returns (CR) or linefeeds (LF) within columns or elements
  • All data are encoded UTF-8

 

The contents of all formats (CSV, JSON, XML) are grouped in the following categories:

 

Output format CSV

This data type means that tabular formats contain more than one table, because objects refer to each other. Such formats always have a unique identifier for each sentence and reference these identifiers from sentences linked to them.

The CSV format is a tabular format written by ITscope as follows:

  • Data is always compressed and is provided as a ZIP package
  • Records are separated by line breaks (CRLF).
  • Fields are separated by tab (\ t).
  • The first line consists of the field names, also separated by tab (\ t).
  • Character strings have no quoting, ie no quoting of the individual columns by ( " )
  • Within character strings neither tabulators, nor line breaks appear.
  • Floating point numbers contain a decimal point and no thousands separator.
  • Date values ​​are as "dd.MM.yyyy hh: mm", as in "12.05.2013 08:02".
  • CSV files are UTF-8 encoded.

CSV downloads are delivered as a compressed zip file. Multi-File CSV formats contain several CSV files that reference each other in the ZIP archive. Even in cases where only a single file is delivered as a result, the ZIP archive can contain several files.

  • Log.csv: contains a list of the products that have been filtered out and the reason for this filtering - this information is intended for ITscope support in order to be able to better research problems.
  • ERROR.txt: exists if errors have occurred; The file is not included in an error-free export; The file is present, but the reason could not be determined.

 

Output Format XML

Hierarchical formats contain all information, but the corresponding objects are subordinate to the referencing object embedded in the parent.


XML is a hierarchical format in which a parent object embeds subordinate objects.

The field names are used as names for the XML elements. Referenced objects have already been resolved and are directly integrated into the parent element.

XML files are transferred directly without additional files and are compressed to HTTP gzip. They can be viewed directly in the browser via the browser. The log information on filtered products are attached as <log> elements at the end.

 

Output format JSON

JSON, like XML, is a hierarchical format that uses a more space-saving syntax. The two formats are very similar in structure.

JSON is a hierarchical format in which a parent object embeds subordinate objects.

The field names are used as names for the JSON elements. Referenced objects have already been resolved and are directly integrated into the parent element.

JSON files are directly transferred without additional files and are compressed to HTTP gzip. They can be viewed directly in the browser via the browser. The log information on filtered products are attached as <log> elements at the end

Note: This page has been translated with the Google Translation Service.

Have more questions? Submit a request