{"_id":"56b2310c65ddf50d0076ba4e","__v":0,"initVersion":{"_id":"56a3a52e5e57f20d000eae28","version":"1.0"},"project":"562e25f2e01a430d00c2c91e","user":{"_id":"562e25d24376430d006f1769","username":"","name":"The API Guys"},"hidden":false,"createdAt":"2016-02-03T16:55:40.820Z","fullscreen":false,"htmlmode":false,"html":"","body":"Jet only supports the current release version of the API. Please find a summary of the upcoming API changes below:\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Upcoming Changes\"\n}\n[/block]\nThe following changes will be made on **Monday, May 29th 2017**:\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Change Description\",\n    \"h-1\": \"Endpoints Affected\",\n    \"2-1\": \"GET merchant SKU endpoint\",\n    \"2-0\": \"Implementation of GET Schemas: \\n\\n* A GET request to this endpoint will only return information about the merchant SKU (inventory and price information must now be accessed via the appropriate endpoints). As such, the following fields will no longer be returned: \\n  * \\\"inventory_by_fulfillment_node\\\"\\n  * \\\"inventory_last_update\\\"\\n  * \\\"price\\\"\\n  * \\\"price_last_update\\\"\\n  * \\\"best_marketplace_offer\\\"\\n  * \\\"my_best_offer\\\" \\n  * \\\"producer_id\\\"\\n  * \\\"merchant_sku_id\\\"\\n  * \\\"merchant_id\\\"\\n  * \\\"jet_sku\\\"\\n  * \\\"correlation_id\\\"\\n  * \\\"sales_rank\\\"\\n  * \\\"sku_created_date\\\" \",\n    \"3-1\": \"Order shipped endpoint\",\n    \"3-0\": \"Additional Validation of Tracking Numbers:\\n\\n* **Validate Against TBA Tracking**: Transportation by Amazon (TBA) tracking numbers will no longer be accepted.\\n\\n* **Validate Against Concatenated Tracking Numbers**: Multiple, concatenated tracking numbers should not be sent for an individual SKU.\",\n    \"0-0\": \"Validate Jet Browse Node ID: \\n\\n* The \\\"jet_browse_node_id\\\" uploaded in a merchant SKU payload must be a real node in the Jet taxonomy. NOTE: the field remains optional.\",\n    \"0-1\": \"Merchant SKU endpoint and file uploads\",\n    \"1-0\": \"Additional Validation of Shipping Exceptions:\\n\\n* For the sake of clarity and efficiency, shipping exception uploads must now adhere to the following rules: \\n\\n  * Restricted exceptions must be associated with methods that are enabled by the merchant at the fulfillment node\\n  * A merchant cannot restrict all methods at a fulfillment node\\n  * If an Exclusive exception is specified at a node, then an Include exception cannot be listed at that same fulfillment node\\n  * If an Exclusive exception is specified at a node, then a Restricted exception cannot be listed at that same fulfillment node\",\n    \"1-1\": \"Shipping exception endpoint and file uploads\"\n  },\n  \"cols\": 2,\n  \"rows\": 4\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Past Changes\"\n}\n[/block]\nThe following changes were released on **Monday, April 10th 2017**:\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Change Description\",\n    \"h-1\": \"Endpoints Affected\",\n    \"0-0\": \"Shipment Message Validation Changes:\\n* **Validate Response Shipment Method**: The \\\"response_shipment_method\\\" value will have to be a [valid value](https://developer.jet.com/docs/ship-order). It will not, however, have to match the \\\"request_shipping_method\\\" from the order_ready payload.  \\n\\n* **Validate Return Location**: The \\\"return_location\\\" value cannot be Jet HQ and cannot have placeholder values (e.g. zip code of \\\"00000\\\") - it must be a real, non-Jet address. Note: this field will remain optional.\\n\\n* **Validate Days to Return**: The \\\"days_to_return\\\" value cannot be less than 7. \\n\\n* **Validate Against Cancelling in Full and Sending Shipment Tracking Number**: The \\\"shipment_tracking_number\\\" must not be populated for any shipment message which contains a total \\\"response_shipment_sku_quantity\\\" of 0. \\n\\n* **Validate Merchant SKU in Ship Message**: The \\\"merchant_sku\\\" in any shipment item must have appeared in the original order. \\n\\n* **Validate Format for Any DateTime Fields**: The \\\"response_shipment_date,\\\" \\\"carrier_pickup_date,\\\" and \\\"expected_delivery_date\\\" must adhere to ISO 8601 format, YYYY-MM-DDThh:mm:ss.fffffff-hh:mm.\",\n    \"0-1\": \"Order shipped endpoint\",\n    \"3-0\": \"Retention Policies:\\n* **Uploaded Files**: Uploaded files will only be accessible for 30 days after upload. \\n\\n* **Order Information**: Orders will only be available by status for 90 days after order creation.\",\n    \"3-1\": \"GET files endpoint and GET orders by status endpoint\",\n    \"1-0\": \"Removal of Acknowledgement and Shipment Message Fields:\\n\\n* **Remove shipment ID and shipment item ID**:  In the order acknowledgment and order shipped messages, Jet will be removing \\\"shipment_id\\\" and \\\"shipment_item_id\\\".  They are obsolete.\",\n    \"1-1\": \"Order acknowledgment and order shipped endpoints\",\n    \"2-0\": \"Deprecation of Endpoints: \\n\\n* **JSON settlement detail reports**: Jet is no longer supporting the JSON order and refund level settlement report.  Jet will now use the bulk reporting API.  The file will be in a csv format, the same way a retailer would receive it by going to the settlement page in the Partner Portal.\",\n    \"2-1\": \"Settlement order detail reports have been removed from the documentation.  Please move to bulk reporting API:\\nhttps://developer.jet.com/docs/create-new-report\"\n  },\n  \"cols\": 2,\n  \"rows\": 4\n}\n[/block]\nThe following changes were released on **Monday, February 20th 2017**:\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Change Description\",\n    \"h-1\": \"Endpoints Affected\",\n    \"0-0\": \"Products API Response Code changes:\\n1. **Successful product updates will now get response code '202' accepted**: To account for changes in SKU processing, Jet will be changing the response codes from 204 to 202.  For the file workflow, \\\"Processed Successfully\\\" will mean that Jet has accepted the product updates.  Jet will provide SLAs around when retailers can expect updates to be reflected on those products.\\n2. **Archive message error message**: When archiving a SKU, Jet currently returns a 204 message for any subsequent SKU update.  If the SKU is archived, Jet will now return a 400 error message stating that the SKU cannot be updated.\",\n    \"0-1\": \"Changes are applied to all endpoints supporting PUT in the Products API section.\",\n    \"1-0\": \"Deprecation of endpoints:\\n* **Deprecate DirectedCancel**: Jet is no longer supporting the directed cancel endpoint.  It is no longer in use.\\n* **Deprecate Upload Image**: Jet is no longer supporting image uploads endpoint.  Image uploads take place as part of the SKU upload.  \\n* **Deprecate SKUs byStatus**: If you are still using the SKUs by status endpoint, please move to bulk reporting API to learn about the status of your SKUs\",\n    \"2-0\": \"**Change Settlement fields to lowercase**: The csv settlement reports provided will have lowercase identifiers to be consistent with the identifiers in the documentation and API.\",\n    \"1-1\": \"Directed cancel endpoint: https://developer.jet.com/docs/directed-cancel\\n\\nImage upload endpoint: \\nhttps://developer.jet.com/docs/merchant-sku-image\\n\\nProductStatus bulk report:\\nhttps://developer.jet.com/docs/create-new-report\",\n    \"2-1\": \"Settlement order report in bulk reporting API: https://developer.jet.com/docs/create-new-report\"\n  },\n  \"cols\": 2,\n  \"rows\": 3\n}\n[/block]\nThe following changes were released on **Wednesday, June 1st**. \n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Change Description\",\n    \"h-1\": \"Endpoints Affected\",\n    \"0-0\": \"**Deprecation of SKUs byStatus endpoint**: Retailers who use the GET /merchant-skus/byStatus endpoint for retrieving product status should move to the bulk reporting API to retrieve product statuses.  Over time, Jet will be adding other report types to this framework\",\n    \"1-0\": \"**Deprecation of Return Acknowledgement Endpoint**: Retailers in the return workflow will only be required to complete a return when a package arrives back at their facility.\",\n    \"0-1\": \"byStatus endpoint has been removed from documentation.  Please move to bulk reporting: http://developer.jet.com/v1.02/docs/create-new-report\",\n    \"1-1\": \"Please make sure you are properly integrated with:\\n \\nOrders Shipped:\\nhttp://developer.jet.com/v1.02/docs/ship-order\\n \\nReturns Exception:\\nhttp://developer.jet.com/v1.02/docs/creating-a-returns-exception\\n \\nReturn Complete: http://developer.jet.com/v1.02/docs/complete-return\"\n  },\n  \"cols\": 2,\n  \"rows\": 2\n}\n[/block]\n\nThe following changes were released on **Monday, May 16th**.  \n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Change Description\",\n    \"h-1\": \"Endpoints Affected\",\n    \"0-0\": \"**Deprecation of \\\"Type\\\" Map Implementation**: In an early API implementation, Jet accepted four different map_implementation values for pricing controls before moving to the 101, 102, 103 values.  Jet asks that any retailers still sending map_implementation with \\\"type\\\" values to map their pricing controls to the following values:\\n \\n'Type0' is closest to '101' \\n'Type1' is closest to '101'\\n'Type2' is closest to '102'\\n'Type3' is closest to '103'\\n'Type4' is closest to '103'\\n \\nPlease note that this change will not apply to all retailers.\",\n    \"0-1\": \"Product Update/File Upload: http://developer.jet.com/v1.02/docs/merchant-sku\",\n    \"1-0\": \"**Product Tax Code Validation**: Jet will enforce the product_tax_code valid values as stated on the developer portal.  This will not affect retailers who are not sending product_tax_code in their product feed\",\n    \"2-0\": \"**Deprecation of \\\"Relationship\\\" Endpoint and \\\"Relationship\\\" File Type**: Jet will deprecate the \\\"relationship\\\" endpoint and \\\"relationship\\\" file type.  Retailers should be using the \\\"variation\\\" endpoint and \\\"variation\\\" file type, which mirrors the implementation.  The key difference between the two is that the “variation” endpoint will accept an array of values. The relationship endpoint only allowed a single value in the variation_refinements field.\",\n    \"3-0\": \"**Acknowledging Every Order Item**: Under all scenarios, retailers should be acknowledging every order item in the order with a \\\"fulfillable\\\" or \\\"nonfulfillable\\\" order_item_acknowledgement_status.  This change will enforce that retailers are sending acknowledgements for all order items\",\n    \"3-1\": \"Order Acknowledgement: http://developer.jet.com/v1.02/docs/acknowledge-order\",\n    \"2-1\": \"Product Variation: http://developer.jet.com/v1.02/docs/merchant-sku-variation\\n \\nUploaded Files: http://developer.jet.com/v1.02/docs/uploaded-files\",\n    \"1-1\": \"Product Update/File Upload: http://developer.jet.com/v1.02/docs/merchant-sku\"\n  },\n  \"cols\": 2,\n  \"rows\": 4\n}\n[/block]\n\nThe following changes were released on **Monday, May 2nd**. \n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Change Description\",\n    \"h-1\": \"Endpoints Affected\",\n    \"h-2\": \"Expected Release Date\",\n    \"h-3\": \"Released\",\n    \"0-0\": \"**New Customer Return/Refund Reasons**:  Jet.com will be adding new customer return reasons and removing old return reasons from the API.  This will improve Jet's tracking of customer related returns issues.  Please update any mappings from Jet's customer return reason to the retailer's return reasons.\",\n    \"0-1\": \"Return Details: http://developer.jet.com/v1.02/docs/check-return-info\\n \\nCreate New Refund: http://developer.jet.com/v1.02/docs/merchant-initiated-refund\",\n    \"0-2\": \"\",\n    \"h-4\": \"\",\n    \"1-0\": \"**Polling for Refunds Links**: When polling for refund links, Jet will currently accept any value in the parameter of the call. This will return all refunds regardless of its current state. This fix will validate the parameter and only return refunds within the state provided in the call. Valid values are located in the link provided.\",\n    \"2-0\": \"**Ambiguous Ship/Cancel Scenario**: When shipping a single unit of a product, Jet accepts a \\\"response_shipment_sku_quantity\\\" of 1 AND a \\\"response_shipment_cancel_qty\\\" of 1.  Jet will begin to validate against this case to prevent SKUs from being ambiguously shipped / cancelled.\",\n    \"1-1\": \"Get Refund Links: http://developer.jet.com/v1.02/docs/check-refund-status\",\n    \"2-1\": \"Orders Shipped: http://developer.jet.com/v1.02/docs/ship-order\",\n    \"3-0\": \"**Requiring Brand and Image**: Jet will now require brand and main_image_url for all products in the product feed.\",\n    \"3-1\": \"Products: \\nhttp://developer.jet.com/v1.02/docs/merchant-sku\"\n  },\n  \"cols\": 2,\n  \"rows\": 4\n}\n[/block]\nThe following changes were released on **March 1st, 2016**:\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Change Description\",\n    \"h-1\": \"Endpoints Affected\",\n    \"h-2\": \"Expected Release Date\",\n    \"h-3\": \"Released\",\n    \"0-0\": \"Shipping Exception Validation: \\n\\nhttps://developer.jet.com/v1.01/docs/merchant-sku-shipping-exception\",\n    \"0-1\": \"/merchant-skus/{user_defined_sku_id}/shippingexception\",\n    \"0-2\": \"March 1st, 2016\",\n    \"0-3\": \"March 1st, 2016\"\n  },\n  \"cols\": 2,\n  \"rows\": 1\n}\n[/block]","slug":"api-release-schedule","title":"API Change Schedule"}

API Change Schedule


Jet only supports the current release version of the API. Please find a summary of the upcoming API changes below: [block:api-header] { "type": "basic", "title": "Upcoming Changes" } [/block] The following changes will be made on **Monday, May 29th 2017**: [block:parameters] { "data": { "h-0": "Change Description", "h-1": "Endpoints Affected", "2-1": "GET merchant SKU endpoint", "2-0": "Implementation of GET Schemas: \n\n* A GET request to this endpoint will only return information about the merchant SKU (inventory and price information must now be accessed via the appropriate endpoints). As such, the following fields will no longer be returned: \n * \"inventory_by_fulfillment_node\"\n * \"inventory_last_update\"\n * \"price\"\n * \"price_last_update\"\n * \"best_marketplace_offer\"\n * \"my_best_offer\" \n * \"producer_id\"\n * \"merchant_sku_id\"\n * \"merchant_id\"\n * \"jet_sku\"\n * \"correlation_id\"\n * \"sales_rank\"\n * \"sku_created_date\" ", "3-1": "Order shipped endpoint", "3-0": "Additional Validation of Tracking Numbers:\n\n* **Validate Against TBA Tracking**: Transportation by Amazon (TBA) tracking numbers will no longer be accepted.\n\n* **Validate Against Concatenated Tracking Numbers**: Multiple, concatenated tracking numbers should not be sent for an individual SKU.", "0-0": "Validate Jet Browse Node ID: \n\n* The \"jet_browse_node_id\" uploaded in a merchant SKU payload must be a real node in the Jet taxonomy. NOTE: the field remains optional.", "0-1": "Merchant SKU endpoint and file uploads", "1-0": "Additional Validation of Shipping Exceptions:\n\n* For the sake of clarity and efficiency, shipping exception uploads must now adhere to the following rules: \n\n * Restricted exceptions must be associated with methods that are enabled by the merchant at the fulfillment node\n * A merchant cannot restrict all methods at a fulfillment node\n * If an Exclusive exception is specified at a node, then an Include exception cannot be listed at that same fulfillment node\n * If an Exclusive exception is specified at a node, then a Restricted exception cannot be listed at that same fulfillment node", "1-1": "Shipping exception endpoint and file uploads" }, "cols": 2, "rows": 4 } [/block] [block:api-header] { "type": "basic", "title": "Past Changes" } [/block] The following changes were released on **Monday, April 10th 2017**: [block:parameters] { "data": { "h-0": "Change Description", "h-1": "Endpoints Affected", "0-0": "Shipment Message Validation Changes:\n* **Validate Response Shipment Method**: The \"response_shipment_method\" value will have to be a [valid value](https://developer.jet.com/docs/ship-order). It will not, however, have to match the \"request_shipping_method\" from the order_ready payload. \n\n* **Validate Return Location**: The \"return_location\" value cannot be Jet HQ and cannot have placeholder values (e.g. zip code of \"00000\") - it must be a real, non-Jet address. Note: this field will remain optional.\n\n* **Validate Days to Return**: The \"days_to_return\" value cannot be less than 7. \n\n* **Validate Against Cancelling in Full and Sending Shipment Tracking Number**: The \"shipment_tracking_number\" must not be populated for any shipment message which contains a total \"response_shipment_sku_quantity\" of 0. \n\n* **Validate Merchant SKU in Ship Message**: The \"merchant_sku\" in any shipment item must have appeared in the original order. \n\n* **Validate Format for Any DateTime Fields**: The \"response_shipment_date,\" \"carrier_pickup_date,\" and \"expected_delivery_date\" must adhere to ISO 8601 format, YYYY-MM-DDThh:mm:ss.fffffff-hh:mm.", "0-1": "Order shipped endpoint", "3-0": "Retention Policies:\n* **Uploaded Files**: Uploaded files will only be accessible for 30 days after upload. \n\n* **Order Information**: Orders will only be available by status for 90 days after order creation.", "3-1": "GET files endpoint and GET orders by status endpoint", "1-0": "Removal of Acknowledgement and Shipment Message Fields:\n\n* **Remove shipment ID and shipment item ID**: In the order acknowledgment and order shipped messages, Jet will be removing \"shipment_id\" and \"shipment_item_id\". They are obsolete.", "1-1": "Order acknowledgment and order shipped endpoints", "2-0": "Deprecation of Endpoints: \n\n* **JSON settlement detail reports**: Jet is no longer supporting the JSON order and refund level settlement report. Jet will now use the bulk reporting API. The file will be in a csv format, the same way a retailer would receive it by going to the settlement page in the Partner Portal.", "2-1": "Settlement order detail reports have been removed from the documentation. Please move to bulk reporting API:\nhttps://developer.jet.com/docs/create-new-report" }, "cols": 2, "rows": 4 } [/block] The following changes were released on **Monday, February 20th 2017**: [block:parameters] { "data": { "h-0": "Change Description", "h-1": "Endpoints Affected", "0-0": "Products API Response Code changes:\n1. **Successful product updates will now get response code '202' accepted**: To account for changes in SKU processing, Jet will be changing the response codes from 204 to 202. For the file workflow, \"Processed Successfully\" will mean that Jet has accepted the product updates. Jet will provide SLAs around when retailers can expect updates to be reflected on those products.\n2. **Archive message error message**: When archiving a SKU, Jet currently returns a 204 message for any subsequent SKU update. If the SKU is archived, Jet will now return a 400 error message stating that the SKU cannot be updated.", "0-1": "Changes are applied to all endpoints supporting PUT in the Products API section.", "1-0": "Deprecation of endpoints:\n* **Deprecate DirectedCancel**: Jet is no longer supporting the directed cancel endpoint. It is no longer in use.\n* **Deprecate Upload Image**: Jet is no longer supporting image uploads endpoint. Image uploads take place as part of the SKU upload. \n* **Deprecate SKUs byStatus**: If you are still using the SKUs by status endpoint, please move to bulk reporting API to learn about the status of your SKUs", "2-0": "**Change Settlement fields to lowercase**: The csv settlement reports provided will have lowercase identifiers to be consistent with the identifiers in the documentation and API.", "1-1": "Directed cancel endpoint: https://developer.jet.com/docs/directed-cancel\n\nImage upload endpoint: \nhttps://developer.jet.com/docs/merchant-sku-image\n\nProductStatus bulk report:\nhttps://developer.jet.com/docs/create-new-report", "2-1": "Settlement order report in bulk reporting API: https://developer.jet.com/docs/create-new-report" }, "cols": 2, "rows": 3 } [/block] The following changes were released on **Wednesday, June 1st**. [block:parameters] { "data": { "h-0": "Change Description", "h-1": "Endpoints Affected", "0-0": "**Deprecation of SKUs byStatus endpoint**: Retailers who use the GET /merchant-skus/byStatus endpoint for retrieving product status should move to the bulk reporting API to retrieve product statuses. Over time, Jet will be adding other report types to this framework", "1-0": "**Deprecation of Return Acknowledgement Endpoint**: Retailers in the return workflow will only be required to complete a return when a package arrives back at their facility.", "0-1": "byStatus endpoint has been removed from documentation. Please move to bulk reporting: http://developer.jet.com/v1.02/docs/create-new-report", "1-1": "Please make sure you are properly integrated with:\n \nOrders Shipped:\nhttp://developer.jet.com/v1.02/docs/ship-order\n \nReturns Exception:\nhttp://developer.jet.com/v1.02/docs/creating-a-returns-exception\n \nReturn Complete: http://developer.jet.com/v1.02/docs/complete-return" }, "cols": 2, "rows": 2 } [/block] The following changes were released on **Monday, May 16th**. [block:parameters] { "data": { "h-0": "Change Description", "h-1": "Endpoints Affected", "0-0": "**Deprecation of \"Type\" Map Implementation**: In an early API implementation, Jet accepted four different map_implementation values for pricing controls before moving to the 101, 102, 103 values. Jet asks that any retailers still sending map_implementation with \"type\" values to map their pricing controls to the following values:\n \n'Type0' is closest to '101' \n'Type1' is closest to '101'\n'Type2' is closest to '102'\n'Type3' is closest to '103'\n'Type4' is closest to '103'\n \nPlease note that this change will not apply to all retailers.", "0-1": "Product Update/File Upload: http://developer.jet.com/v1.02/docs/merchant-sku", "1-0": "**Product Tax Code Validation**: Jet will enforce the product_tax_code valid values as stated on the developer portal. This will not affect retailers who are not sending product_tax_code in their product feed", "2-0": "**Deprecation of \"Relationship\" Endpoint and \"Relationship\" File Type**: Jet will deprecate the \"relationship\" endpoint and \"relationship\" file type. Retailers should be using the \"variation\" endpoint and \"variation\" file type, which mirrors the implementation. The key difference between the two is that the “variation” endpoint will accept an array of values. The relationship endpoint only allowed a single value in the variation_refinements field.", "3-0": "**Acknowledging Every Order Item**: Under all scenarios, retailers should be acknowledging every order item in the order with a \"fulfillable\" or \"nonfulfillable\" order_item_acknowledgement_status. This change will enforce that retailers are sending acknowledgements for all order items", "3-1": "Order Acknowledgement: http://developer.jet.com/v1.02/docs/acknowledge-order", "2-1": "Product Variation: http://developer.jet.com/v1.02/docs/merchant-sku-variation\n \nUploaded Files: http://developer.jet.com/v1.02/docs/uploaded-files", "1-1": "Product Update/File Upload: http://developer.jet.com/v1.02/docs/merchant-sku" }, "cols": 2, "rows": 4 } [/block] The following changes were released on **Monday, May 2nd**. [block:parameters] { "data": { "h-0": "Change Description", "h-1": "Endpoints Affected", "h-2": "Expected Release Date", "h-3": "Released", "0-0": "**New Customer Return/Refund Reasons**: Jet.com will be adding new customer return reasons and removing old return reasons from the API. This will improve Jet's tracking of customer related returns issues. Please update any mappings from Jet's customer return reason to the retailer's return reasons.", "0-1": "Return Details: http://developer.jet.com/v1.02/docs/check-return-info\n \nCreate New Refund: http://developer.jet.com/v1.02/docs/merchant-initiated-refund", "0-2": "", "h-4": "", "1-0": "**Polling for Refunds Links**: When polling for refund links, Jet will currently accept any value in the parameter of the call. This will return all refunds regardless of its current state. This fix will validate the parameter and only return refunds within the state provided in the call. Valid values are located in the link provided.", "2-0": "**Ambiguous Ship/Cancel Scenario**: When shipping a single unit of a product, Jet accepts a \"response_shipment_sku_quantity\" of 1 AND a \"response_shipment_cancel_qty\" of 1. Jet will begin to validate against this case to prevent SKUs from being ambiguously shipped / cancelled.", "1-1": "Get Refund Links: http://developer.jet.com/v1.02/docs/check-refund-status", "2-1": "Orders Shipped: http://developer.jet.com/v1.02/docs/ship-order", "3-0": "**Requiring Brand and Image**: Jet will now require brand and main_image_url for all products in the product feed.", "3-1": "Products: \nhttp://developer.jet.com/v1.02/docs/merchant-sku" }, "cols": 2, "rows": 4 } [/block] The following changes were released on **March 1st, 2016**: [block:parameters] { "data": { "h-0": "Change Description", "h-1": "Endpoints Affected", "h-2": "Expected Release Date", "h-3": "Released", "0-0": "Shipping Exception Validation: \n\nhttps://developer.jet.com/v1.01/docs/merchant-sku-shipping-exception", "0-1": "/merchant-skus/{user_defined_sku_id}/shippingexception", "0-2": "March 1st, 2016", "0-3": "March 1st, 2016" }, "cols": 2, "rows": 1 } [/block]