Update changelog readme for Oauth (iZettle#147)

* Updated CHANGELOG and README with changes about get-started and OAuth flow.

Author: Astro-Choco

CHANGELOG.adoc

@@ -7,14 +7,19 @@ Each log entry uses the following tags:
 - For API changes and the corresponding documentation changes, the log is tagged with the name of the changes API. For example, `OAuth API`.
 - For documentation changes that are editorial and are not introduced by any API change, the log is tagged with `Editorial changes`.
 
-.**February 3, 2022** `Inventory API`
+.**February 3, 2022** `Inventory API` `OAuth API` `Get started`
 [%collapsible]
 ====
-**Extended documentation with these additions:**
+**Extended Inventory API documentation with these additions:**
 
 - Overview of Inventory API.
 - Concept description - how inventories work.
 - User guides for managing locations, tracking, inventory balances, and low stock levels.
+
+**Added how to get started with Zettle APIs:**
+
+- A user guide for signing up for a developer account.
+- Users guides for setting up authorisation flows.
 ====
 
 .**January 18, 2022** `OAuth API` `Editorial changes`

README.md

@@ -38,9 +38,12 @@ All API incidents are recorded in [Incidents](incidents.md).
 
 For common questions about the APIs, see [Frequently Asked Questions](faq.adoc).
 
-## Credentials
+## Get started
+Before you start to build an app with Zettle, you need to [sign up for a developer account at Zettle Developer Portal](get-started/user-guides/sign-up-for-a-developer-account.md).
 
-Apply for API credentials on [Zettle Developer Portal](https://developer.zettle.com/register).
+When you have a developer account, choose one of the following app types based on your needs:
+* To build a self-hosted app that is hosted by merchants individually, [create a self-hosted app](oauth-api/user-guides/create-an-app/create-a-self-hosted-app/create-a-self-hosted-app.md).
+* To build a partner-hosted app that is hosted by you as an integrator, [create a partner-hosted app](oauth-api/user-guides/create-an-app/create-a-partner-hosted-app.md).
 
 ## Get help
 Contact our [Integrations team](mailto:[email protected]) for more information. 

get-started/user-guides/sign-up-for-a-developer-account.md

@@ -19,7 +19,7 @@ Before you start to build an app with Zettle, you need to sign up for a Zettle d
    After that, you will receive a welcome email from Zettle with the Developer Platform Agreement. Now you're ready to start building with Zettle.
 
 ## Next task
-* To build a self-hosted app that is hosted by merchants individually, [create a self-hosted app](../../oauth-api/user-guides/create-an-app/create-a-self-hosted-app).
+* To build a self-hosted app that is hosted by merchants individually, [create a self-hosted app](../../oauth-api/user-guides/create-an-app/create-a-self-hosted-app/create-a-self-hosted-app.md).
 * To build a partner-hosted app that is hosted by you as an integrator, [create a partner-hosted app](../../oauth-api/user-guides/create-an-app/create-a-partner-hosted-app.md).
 
 ## Related API reference

oauth-api/user-guides/create-an-app/create-a-partner-hosted-app.md

@@ -5,7 +5,7 @@ A partner-hosted app is hosted by you as an integrator. To authorise, the app us
 In an authorisation code grant flow, you use a temporary authorisation code to exchange for an access token from the authorisation server. A temporary authorisation code is generated from the authorisation server using API credentials. API credentials include a client secret and client ID.
 
 To authorise your app using authorisation code grant, you need to get API credentials for the app by creating an app in your Dashboard on the [Developer Portal](https://developer.zettle.com/).
-> **Note:** If you want to build a self-hosted app that will be hosted by merchants, [create a self-hosted app](create-a-self-hosted-app).
+> **Note:** If you want to build a self-hosted app that will be hosted by merchants, [create a self-hosted app](create-a-self-hosted-app/create-a-self-hosted-app.md).
 
 * [Prerequisites](#prerequisites)
 * [Get API credentials for a new app](#get-api-credentials-for-a-new-app)

oauth-api/user-guides/create-an-app/create-a-self-hosted-app/create-a-self-hosted-app.md

@@ -3,9 +3,8 @@ Create a self-hosted app
 A self-hosted app is hosted by one or more merchants individually. To authorise, the app uses the authorisation assertion grant.
 
 In an authorisation assertion grant flow, you use a JSON web token (JWT) assertion to request an access token from the authorisation server. The JWT assertion is used as an API key. An API key is created by a merchant (Zettle merchant account owner). It's valid until the merchant revokes it.
-<!-- add assertion grant in glossary -->
 
-To authorise your app using assertion grant, you need to ask the merchant (Zettle merchant account owner) to create an API key at my.zettle.com. You can provide the merchant a deep link that directs them to the API creation page or steps to create an API key.
+To authorise your app using assertion grant, you need to ask the merchant (Zettle merchant account owner) to create an API key at my.zettle.com. You can provide the merchant a link that directs them to the API creation page or steps to create an API key.
 
 > **Note:** If you want to build a partner-hosted app that will be hosted by you as an integrator, [create a partner-hosted app](../create-a-partner-hosted-app.md).
 
@@ -22,7 +21,7 @@ To authorise your app using assertion grant, you need to ask the merchant (Zettl
 An API key must be created by the Zettle merchant that will use your app.
 
 1. Ask the merchant to create an API key in one of the following ways:
-   * Provide the merchant a deep link with pre-populated fields and [the instructions to create an API key with the deep link](create-an-api-key.md#create-an-api-key-with-a-deep-link-from-the-developer).
+   * Provide the merchant a link with pre-populated fields and [the instructions to create an API key with the link](create-an-api-key.md#create-an-api-key-with-a-link-from-the-developer).
       ```
       https://my.zettle.com/apps/api-keys?name=<key-name>&scopes=<scopes>
       ```

oauth-api/user-guides/set-up-app-authorisation/set-up-authorisation-assertion-grant.md

@@ -12,7 +12,7 @@ To build a self-hosted app with APIs, you need to set up the authorisation asser
 ## Prerequisites
 * You have an account for the [Developer Portal](https://developer.zettle.com/). If you don't have an account, [sign up for a developer account](../../../get-started/user-guides/sign-up-for-a-developer-account.md).
 
-* You have an API key and a client ID for the app. If you don't have any, [create a self-hosted app](../create-an-app/create-a-self-hosted-app).
+* You have an API key and a client ID for the app. If you don't have any, [create a self-hosted app](../create-an-app/create-a-self-hosted-app/create-a-self-hosted-app.md).
 
 ## Step 1: Retrieve an access token from an API key
 To retrieve a short-lived access token from the API key, include the API key and the client ID in the following request.
@@ -46,7 +46,7 @@ An access token is valid only for 7200 seconds. Use the same API key to generate
 
 
 ## Previous task
-* [Create a self-hosted app](../create-an-app/create-a-self-hosted-app)
+* [Create a self-hosted app](../create-an-app/create-a-self-hosted-app/create-a-self-hosted-app.md)
 
 ## Related API reference
 * [OAuth2 API Reference](../../../authorization.md)

oauth-api/user-guides/set-up-app-authorisation/set-up-authorisation-code-grant.md

@@ -87,7 +87,7 @@ An access token is valid only for 7200 seconds. When it expires, use the refresh
    Request   
 
    ```
-   curl -X POST -H "Content-Type: application/x-www-form-urlencoded" -d "grant_type=refresh_token&refresh_token=IZSEC90590831-93a5-4289-ee37-a17824c0fea1&client_secret=IZSECe8b27fdb-faea-46e1-a886-6eded9f84f72}&client_id=6adde977-c34d-4de1-99b2-f6ed3e65431a" https://oauth.zettle.com/token
+   curl -X POST -H "Content-Type: application/x-www-form-urlencoded" -d "grant_type=refresh_token&refresh_token=IZSEC90590831-93a5-4289-ee37-a17824c0fea1&client_secret=IZSECe8b27fdb-faea-46e1-a886-6eded9f84f72&client_id=6adde977-c34d-4de1-99b2-f6ed3e65431a" https://oauth.zettle.com/token
    ```
    Response         
    ```json