The ItemKey JSON object defines uniquely identifies an item without using Dsco's dscoItemId within the Dsco system. One of supplierId or tradingPartnerId must be provided to indicate which Dsco account owns the item and then a key is specified (UPC, SKU, etc.)
- Make sure you're familiar with JSON before continuing.
- The JSON objects are defined using Orderly. Optional attrs end with a "?" all others are required.
- isodate fields use one of these ISO 8601 format: 2014-01-01T10:30:00.000+01:00, 2014-01-01T10:30:00.000+0100, 2014-01-01T10:30:00.000Z
- Dsco reserves the right to add new attributes at any time so Partners should ensure their validators won't break should this happen
Definition
Object { int dscoSupplierId?; # Uniquely identifies the account owning the item # using Dsco's identifier string tradingPartnerId?; # Unqiuely identifies the account owning the item # using the partner's own identifier string itemKeyType[SKU, # Indicates the key is a SKU UPC, # Indicates the key is a UPC EAN, # Indicates the key is an EAN MPN, # Indicates the key is an MPN ISBN, # Indicates the key is an ISBN GTIN, # Indicates the key is a GTIN PARTNER_SKU]; # Indicates the key is a PARTNER_SKU string itemKey; # The identifier itself whose type is # specified by itemKeyType };
Example
{ "dscoSupplierId": 234242, "itemKeyType": "UPC", "key": "s32f232f22" }
Comments
Please sign in to leave a comment.