Merge pull request #652 from akeneo/CPM-724

CPM-724: Add Product Uuids endpoints

Author: pierallard

content/concepts/asset-manager.md

@@ -1930,7 +1930,7 @@ Here are the steps to follow to link assets to your products:
 2. Put this attribute within the [families](/concepts/catalog-structure.html#familiy) of the products you want to link your assets to.
 3. Assign your assets to these products either:
 - manually, in the `Assets` tab of the product form in the PIM UI,
-- by API using the [product](/api-reference.html#patch_products) POST and PATCH endpoints by adding the asset codes in the asset collection data,
+- by API using the [product](/api-reference.html#patch_products_uuid) POST and PATCH endpoints by adding the asset codes in the asset collection data,
 - automatically thanks to the [product link rule](#focus-on-the-product-link-rule), detailed in the paragraph below.
 
 ::: info

content/concepts/products.md

@@ -26,14 +26,21 @@ Below is the JSON standard format representing a product.
 
 ```json
 {
-  "identifier": "1111111195",
+  "uuid": "fc24e6c3-933c-4a93-8a81-e5c703d134d5",
   "family": "clothing",
   "parent": "jack_brown",
   "categories": [
     "tshirts"
   ],
   "enabled": true,
   "values": {
+    "sku": [
+      {
+        "locale": null,
+        "scope": null,
+        "data": "1111111195"
+      }
+    ],
     "ean": [
       {
         "locale": null,
@@ -138,7 +145,7 @@ Note that the `quality_scores` field is only available since the 5.0 and when th
 Note that the `completenesses` field is only available on SaaS platforms, and when the `with_completenesses` query parameter is set to `true`.
 :::
 
-::: panel-link Want more details about the product resource? [Check its endpoints here!](/api-reference.html#Product)
+::: panel-link Want more details about the product resource? [Check its endpoints here!](/api-reference.html#Productuuid)
 :::
 
 ### Convert a variant product to a simple product

content/files/Akeneo PIM API.postman_collection.json

@@ -24,15 +24,15 @@
 					}
 				],
 				"url": {
-					"raw": "{{url}}/api/rest/v1/products",
+					"raw": "{{url}}/api/rest/v1/products-uuid",
 					"host": [
 						"{{url}}"
 					],
 					"path": [
 						"api",
 						"rest",
 						"v1",
-						"products"
+						"products-uuid"
 					]
 				},
 				"description": "This REST API request asks the PIM for its 100 first products."

content/files/your-very-first-collection.postman_collection.json

@@ -62,7 +62,7 @@ _In our example, as stated above, we know that every day, new products are creat
 In this step, you will need to find in our [REST API reference](/api-reference-index.html) the endpoints you need to achieve such a connection. 
 
 #### In this tutorial
-_For our example, you will need to create and update products in the PIM so we will mainly need this endpoint: [Patch](/api-reference.html#patch_products) on products._
+_For our example, you will need to create and update products in the PIM so we will mainly need this endpoint: [Patch](/api-reference.html#patch_products_uuid) on products._
 
 ### 5- Think about your architecture
 Choose the architecture you want for your connector. Indeed, you will have two options here:
@@ -81,7 +81,7 @@ _For our example, we choose the second option as there are little chances that y
 A crucial step. In most cases, you will need to manually map some PIM information with the data sent or received in or from the software you want to connect.
 
 #### In this tutorial
-_For our example, here is the global orchestration of our connector. First, every evening, you will extract the list of products that were created/updated during the day, in an XML file. Then, your connector reads this file. ERP products are then transformed into PIM products, by mapping the ERP information with the right PIM attributes. Lastly, the connector sends the PIM products by using the [patch](/api-reference.html#patch_products) endpoint of our REST API._
+_For our example, here is the global orchestration of our connector. First, every evening, you will extract the list of products that were created/updated during the day, in an XML file. Then, your connector reads this file. ERP products are then transformed into PIM products, by mapping the ERP information with the right PIM attributes. Lastly, the connector sends the PIM products by using the [patch](/api-reference.html#patch_products_uuid) endpoint of our REST API._
 
 ## Some pro tips
 

content/getting-started/connect-the-pim-4x/step-2.md

@@ -58,7 +58,7 @@ _In our example, as stated above, we know that every day, new products are creat
 In this step, you will need to find in our [REST API reference](/api-reference-index.html) the endpoints you need to achieve such a connection. 
 
 #### In this tutorial
-_For our example, you will need to create and update products in the PIM so we will mainly need this endpoint: [Patch](/api-reference.html#patch_products) on products._
+_For our example, you will need to create and update products in the PIM so we will mainly need this endpoint: [Patch](/api-reference.html#patch_products_uuid) on products._
 
 ### 5- Think about your architecture
 Choose the architecture you want for your connector. Indeed, you will have two options here:
@@ -77,7 +77,7 @@ _For our example, we choose the second option as there are little chances that y
 A crucial step. In most cases, you will need to manually map some PIM information with the data sent or received in or from the software you want to connect.
 
 #### In this tutorial
-_For our example, here is the global orchestration of our connector. First, every evening, you will extract the list of products that were created/updated during the day, in an XML file. Then, your connector reads this file. ERP products are then transformed into PIM products, by mapping the ERP information with the right PIM attributes. Lastly, the connector sends the PIM products by using the [patch](/api-reference.html#patch_products) endpoint of our REST API._
+_For our example, here is the global orchestration of our connector. First, every evening, you will extract the list of products that were created/updated during the day, in an XML file. Then, your connector reads this file. ERP products are then transformed into PIM products, by mapping the ERP information with the right PIM attributes. Lastly, the connector sends the PIM products by using the [patch](/api-reference.html#patch_products_uuid) endpoint of our REST API._
 
 ## Some pro tips
 

content/getting-started/connect-the-pim-old/step-1.md

@@ -18,17 +18,17 @@ We recommend to you the following product filters:
 - by family codes (save to your storage in a **family_code_list** during [the second step](/getting-started/synchronize-pim-products-6x/step-2.html));
 - by enabled products (you probably don’t use not enabled products, don’t you?)
 
-Another very important point is the **with_attribute_options**. When this option is activated, labels of attributes options will be returned in the response — and saves you from many extra API calls. More information [here](https://api.akeneo.com/api-reference.html#get_products).
+Another very important point is the **with_attribute_options**. When this option is activated, labels of attributes options will be returned in the response — and saves you from many extra API calls. More information [here](https://api.akeneo.com/api-reference.html#get_products_uuid).
 
 ::: tips
 Have a look at our [product filters](https://api.akeneo.com/documentation/filter.html#filter-on-product-properties): you may find other interesting ones.
 :::
 
 So, what does our API call on products look like?
 
-`GET /api/rest/v1/products?locales=locales&scope=your_channel_code&with_attribute_options=true&search={"family":[{"operator":"IN","value":family_code_list}],"enabled"[{"operator":"=","value":true}]}`
+`GET /api/rest/v1/products-uuid?locales=locales&scope=your_channel_code&with_attribute_options=true&search={"family":[{"operator":"IN","value":family_code_list}],"enabled"[{"operator":"=","value":true}]}`
 
-Details of this call are [here](https://api.akeneo.com/api-reference.html#get_products).
+Details of this call are [here](https://api.akeneo.com/api-reference.html#get_products_uuid).
 
 What is important in the response payload?
 

content/getting-started/synchronize-pim-products-6x/step-4.md

@@ -10,7 +10,7 @@ Alright! You're all set now. Let's launch this request.
 In the response area, you should get an answer similar to the one below.
 ![Response area for authent request](/img/getting-started/authentication-response.png)
 4. Now, click on `Your very first request` in the `Collections` tab.
-5. You can see the request we are about to launch. It is using the endpoint referenced [here](/api-reference.html#get_products). We are going to ask your PIM to give us its first 100 products.
+5. You can see the request we are about to launch. It is using the endpoint referenced [here](/api-reference.html#get_products_uuid). We are going to ask your PIM to give us its first 100 products.
 ![Your very first request](/img/getting-started/your-very-first-request.png)
 6. Are you ready? Hit the blue `Send` button.
 In the response area, you can see a list of 100 products in json format. 

content/getting-started/your-first-tutorial-4x/step-3.md

@@ -10,7 +10,7 @@ Alright! You're all set now. Let's launch this request.
 In the response area, you should get an answer similar to the one below.
 ![Response area for authent request](/img/getting-started/authentication-response.png)
 4. Now, click on `Your very first request` in the `Collections` tab.
-5. You can see the request we are about to launch. It is using the endpoint referenced [here](/api-reference.html#get_products). We are going to ask your PIM to give us its first 100 products.
+5. You can see the request we are about to launch. It is using the endpoint referenced [here](/api-reference.html#get_products_uuid). We are going to ask your PIM to give us its first 100 products.
 ![Your very first request](/img/getting-started/your-very-first-request.png)
 6. Are you ready? Hit the blue `Send` button.
 In the response area, you can see a list of 100 products in json format.

content/getting-started/your-first-tutorial-old/step-3.md

@@ -181,7 +181,7 @@ We suggest that you develop the first solution during the first iteration of you
 :::
 
 :::tips
-Using the ["get a list of products"](https://api.akeneo.com/api-reference.html#get_products) API endpoint (with the correct filter), your App will retrieve a JSON structure of each localizable products.
+Using the ["get a list of products"](https://api.akeneo.com/api-reference.html#get_products_uuid) API endpoint (with the correct filter), your App will retrieve a JSON structure of each localizable products.
 
 Then, with the help of the family code of these products, your App will be able to call the ["get the list of attributes"](https://api.akeneo.com/api-reference.html#get_attributes) API endpoint to retrieve each attribute type that composes this product family.