Merge pull request #80 from magento/2.0_kh_final

2.0 kh final

Author: keharper

guides/v2.0/rest/bk-rest.md

@@ -11,10 +11,7 @@ github_link: rest/bk-rest.md
 redirect_from: /guides/v1.0/rest/bk-rest.html
 ---
 
-The [REST API documentation](http://devdocs.magento.com/swagger/index.html) published here on the Magento 2 Developer Documentation website describes the REST APIs that are available on Magento 2.0 Community Edition. (Currently, there are no APIs specific to Enterprise Edition.) This documentation is generated from the code base using [Swagger](http://swagger.io) and represents the state of the code at the time the documentation was generated. However, the REST API documentation is static in that the Magento Developers website is not running an instance of Magento.
-
-
-The [REST API documentation](http://devdocs.magento.com/swagger/index.html) describes the REST APIs that are available on Magento 2.0 Community Edition. It is generated from the code base and represents the state of the code at the time the documentation was generated.
+The [REST API documentation](http://devdocs.magento.com/swagger/index.html) published here on the Magento 2 Developer Documentation website describes the REST APIs that are available on the latest release of Magento 2 Community Edition.  This documentation is generated from the code base using [Swagger](http://swagger.io) and represents the state of the code at the time the documentation was generated. However, the REST API documentation is static in that the Magento Developers website (devdocs.magento.com) is not running an instance of Magento.
 
 For information about creating a dynamic API documentation set on your server with live data, see
 [Generate local REST API reference

guides/v2.0/rest/generate-local.md

@@ -10,10 +10,28 @@ github_link: rest/generate-local.md
 
 ---
 
-The REST documentation is generated with [Swagger UI](http://swagger.io) using a schema derived from the latest build of Magento 2.0 Community Edition. However, the REST API documentation is static in that the Magento Developers website is not running an instance of Magento.
+The REST documentation is generated with [Swagger UI](http://swagger.io) using a schema derived from the latest build of Magento 2 Community Edition. However, the REST API documentation is static in that the Magento Developers website is not running an instance of Magento.
 
-If you install Swagger UI on your server, then you can generate live REST API documentation. Use the following link to generate a JSON schema that includes third-party modules and extension attributes that have been installed on your system. 
+The REST documentation on the Magento devdocs website is generated with Swagger UI using a schema derived from the latest build of Magento 2 Community Edition. However, the REST API documentation on devdocs is static in that the Magento Developers website is not running an instance of Magento and there is no live data.
+
+The Swagger UI is installed automatically on your server. As a result, you can generate live REST API documentation that can include third-party modules and extension attributes that have been installed on your system. To view this documentation, go to:
+
+`http://<magento_host>/swagger`
+
+You can also use the following link to generate a JSON schema:
 
 `http://<magento_host>/rest/default/schema`
 
-Then save the schema file and load it into your Swagger UI instance.
+To access REST API documentation, Magento requires the user to be authenticated and authorized, as follows:
+
+* By default, Magento returns documentation for resources available to anonymous users.
+* If a customer or admin session is active, Magento returns documentation as permitted by the user's role.
+* To retrieve information for a particular user, you must specify a token in the Authorization request header with the Bearer HTTP authorization scheme.
+
+The generated Swagger documentation provides the capability to test REST API requests. A user can enter a sample request, then press the **Try it out!** button, and Swagger returns information such as a `curl` command, a request URL, a response body, a response code, and the response header. Using the **Try it out!** button also requires a bearer authorization token.
+
+The **Try it out!** feature is not available on Swagger documentation published on the Magento devdocs website.
+
+<div class="bs-callout bs-callout-info" id="info">
+  <p>The <b>Try it out!</b> feature is not available on Swagger documentation published on the Magento devdocs website.</p>
+</div>

guides/v2.0/rest/notes.md

@@ -0,0 +1,24 @@
+---
+layout: default
+group: rest
+subgroup: A_rest
+title: Notes
+menu_title: Notes
+menu_order: 6
+version: 2.0
+github_link: rest/notes.md
+
+---
+
+## Parameters in URLs
+
+In a REST call, a user could potentially specify one ID in the URL and another in the request body. Whenever this type of conflict occurs, Magento uses the value specified in the URL.
+
+For example:
+
+The REST URL to update a customer is `<route url="/V1/customers/:id" method="PUT">`.  If you specify a ID value of `1` in the URL (`http://magento.loc/customer/1`), and a body of `{ “id”: 2, “attr”: “value” }`, the customer with ID of `1` will be modified.
+
+This applies to all REST APIs where a parameter is passed in the URL. Anything specified in the request body with the same parameter name as the URL will be ignored.
+
+## Related topics
+[Search using REST APIs]({{ site.gdeurl }}howdoi/webapi/search-criteria.html)