Product Export:

• Limit the product information you need for faster response and less load
  • Use the query parameter excludeData to specify which parts of the product information you do not want in return:
    • PRODUCT_HEAD
    • ATTRIBUTE
    • TEXT
    • MEDIA
    • RELATION
    • LINKED_TO
    • VARIANT
    • STRUCTURE
    • PACKAGING
    • ETIM
  • By excluding all parts in the list above, only a list of “identifiers” for the products in the export will be returned. This means a list of products that only have feed®'s unique internal ID and possibly the product number on the product.
  • Use the query parameter includeOptions = false to only retrieve selected values on the product and not other options where there are lists of valid choices. This can significantly reduce the data volume per product, especially where there is ETIM data or many data register attributes.
  • Do you only need data from the product head? Then you can also use productHeadOnly = true to only retrieve this information (an alternative to excludeData with everything except PRODUCT_HEAD).

• Search for the products you need
  There are several ways to limit which products are exported. All of these can be combined and will further limit the result (AND, not OR).
  • Specify a list of product numbers, or internal IDs (importCodes) from feed using query parameters:

• • • productNo = “12345”, “23456”, “34567”
    • altProductNo = “12345”, “23456”, “34567”
    • importCodes = “1”, “2”, “3”
  • Limit search results to desired values of product owners, status, product templates (productType), product group, and/or suppliers based on associated import codes:
    • productOwnerImportCodes
    • productStatusImportCodes
    • productTypeImportCodes
    • productGroupImportCodes
    • supplierImportCodes

• • It is also possible to search by name or designation. Note: You must search for whole words; searching for parts of a word in the name will not yield results.
    For example, if you have a product named “adidas Yeezy Boost”, you can search for “adidas”, “Yeezy”, or “Boost”, or a combination of these to find the product. However, searching for “adida” or “Yeez” will not yield results.

• • • name
    • alternativeName
  • It is also possible to search for ETIM values or custom attributes and texts. To do this, you must send a JSON body with search parameters:
    • productSearch

{
  "attributes": [
    {
      "importCode": "kode til attributt du skal søke på",
      "value": "verdi du søker etter"
    }
  ],
  "productTexts": [
    {
      "textSearch": "string",
      "importCode": "string"
    }
  ],
  "etim": {
    "version": 0,
    "etimClassIds": [
      "string"
    ],
    "features": [
      {
        "featureId": "string",
        "value": {}
      }
    ]
  }
}

• • For attribute values, the syntax depends on the data type you are searching for.

    Excerpt from Swagger documentation:

    List of datatypes and how to send them: Integer where range = false: 12 -100 null Integer where range = true: [0, 100] [null, 100] [0, null] [null, null] Float where range = false: 12.3 -100.0 null Float where range = true: [0.0, 99.99] [null, 99.99] [0.0, null] [null, null] Date where range = false: "2019-12-31" null Date where range = true: ["2019-01-01", "2019-12-31"] [null, "2019-12-31"] [2019-01-01", null] [null, null] Text: { "nb": "Dette er en norsk attributtekst.", "en": "This is an English attribute text." } Boolean: true false Data register: "key_1" null Data register multi: ["key_1","key_2","key_2"] []