Dec 9, 2022 · Dec 6, 2022 · Dec 7, 2022 · Dec 7, 2022 · Dec 7, 2022
diff --git a/docs/docs/08_flask_jwt_extended/11_insomnia_request_chaining/README.md b/docs/docs/08_flask_jwt_extended/11_insomnia_request_chaining/README.md

 # Request chaining with Insomnia

 Nothing here yet!
 Up until now, we've been able to log in, get an access token, and then use that acces token to access the protected endpoints in our API. However, this workflow is a bit tedious, and we have to copy-paste the access token into every request. Luckily, Insomnia has a feature called [request chaining](https://support.insomnia.rest/article/26-request-chaining) that allows us to simplify this workflow!

 ## How to use request chaining with Insomnia

 Instead of passing the JWT in every request, you can access the `Headers`  section and follow these steps. In the `Authorization` field, type `Bearer` add a space and then press `CTRL + SPACE` to get a contextual menu. Navigate to the `Response -> Body Attribute` field and select it, as shown in the screenshot below:

 ![Contextual menu with Generator Tag options](./assets/bearer_token.png)

 After you've selected it, you'll see an error that looks like this:

 ![Response error in the Authorization field](./assets/error.png)

 If you click on the error, you'll see a modal window:

 ![Modal window with empty fields](./assets/modal.png)

 Inside of this window, you will first need to select a request that you want to get the data from. Click on `Select item` inside the `Request` field and choose the `POST /login` endpoint. After you've done that, go to the `Filter` field. In this field, we are telling Insomnia which part of the response we want to get from it. The prompt is started with the dollar sign `$` and then we can use the dot to access the attributes of the response. If we only type `$` or `$.`, we'll get a list of all the attributes of the response:

 ![Attributes recieved from request using a dollar sign](./assets/attributes.png)

 In our case, we want to get the `access_token` attribute from the response, so we type `$.access_token`. If there was something else inside the `access_token` that you wanted to access like some value for example, you could do `$.access_token.value` and so on. After you've added the filter, you can set the `Trigger Behavior`. For example, you can set it to `When expired` and set time to 300 seconds. This means that the token will be refreshed every 5 minutes. The filled out window should look like this:

 ![Filled out modal window with attributes recieved from request using a dollar sign followed by .access_token](./assets/filled_out.png)

 You can now press `Done` and you'll see that the error is gone and that the `Authorization` field is filled out with the `Bearer` token:

 ![Filled out Authorization field with Bearer token](./assets/token.png)

 Since we use multiple protected endpoints, we would need to use the same method to get the `access_token` for every request. To tackle this problem, we can use [environment variables](https://support.insomnia.rest/article/13-environment-variables), as we did before for the `url` variable.

 To do this, you need to create a new environment variable. Click on the `No Environment` button in the top left corner of the Insomnia window and then click on the `Manage Environments` button, you will see a base environment that looks like this:

 ![Base environment with url environment variable only](./assets/base_environment.png)

 Add a new environment variable called `access_token`, and for its value you should follow the same process from above. As a quick reminder, you should press `CTRL + SPACE` to get the contextual menu and then select the `Response -> Body Attribute` field. Click on the error that will show up and fill out the modal window as we've done before. Make sure to wrap the `Response -> Body Attribute` with quotation marks, as shown in the screenshot. When the variable is created, your environment should look like this:

 ![Base environment with added access_token variable](./assets/environment.png)

 You will now be able to use this environment variable in all of the endpoints by simply writing `{{access_token}}` in the field that you want to use it in. Coming back to the first example, you can use the access token in the `Authorization` field by writing `Bearer {{access_token}}` and this will be the result:

 ![Bearer with access_token environment variable](./assets/result.png)

 If you try and make the request, you will see that it works just like before, without needing to copy and paste the access token.
diff --git a/docs/docs/08_flask_jwt_extended/11_insomnia_request_chaining/assets/attributes.png b/docs/docs/08_flask_jwt_extended/11_insomnia_request_chaining/assets/attributes.png
diff --git a/.../08_flask_jwt_extended/11_insomnia_request_chaining/assets/base_environment.png b/.../08_flask_jwt_extended/11_insomnia_request_chaining/assets/base_environment.png
diff --git a/...docs/08_flask_jwt_extended/11_insomnia_request_chaining/assets/bearer_token.png b/...docs/08_flask_jwt_extended/11_insomnia_request_chaining/assets/bearer_token.png
diff --git a/.../docs/08_flask_jwt_extended/11_insomnia_request_chaining/assets/environment.png b/.../docs/08_flask_jwt_extended/11_insomnia_request_chaining/assets/environment.png
diff --git a/docs/docs/08_flask_jwt_extended/11_insomnia_request_chaining/assets/error.png b/docs/docs/08_flask_jwt_extended/11_insomnia_request_chaining/assets/error.png
diff --git a/docs/docs/08_flask_jwt_extended/11_insomnia_request_chaining/assets/filled_out.png b/docs/docs/08_flask_jwt_extended/11_insomnia_request_chaining/assets/filled_out.png
diff --git a/docs/docs/08_flask_jwt_extended/11_insomnia_request_chaining/assets/modal.png b/docs/docs/08_flask_jwt_extended/11_insomnia_request_chaining/assets/modal.png
diff --git a/docs/docs/08_flask_jwt_extended/11_insomnia_request_chaining/assets/result.png b/docs/docs/08_flask_jwt_extended/11_insomnia_request_chaining/assets/result.png
diff --git a/docs/docs/08_flask_jwt_extended/11_insomnia_request_chaining/assets/token.png b/docs/docs/08_flask_jwt_extended/11_insomnia_request_chaining/assets/token.png
diff --git a/package-lock.json b/package-lock.json
Original file line number	Diff line number	Diff line change
Expand Up		@@ -5,4 +5,46 @@ description: "Learn how to use Insomnia's Request Chaining to simplify our workf

		# Request chaining with Insomnia

		Nothing here yet!
		Up until now, we've been able to log in, get an access token, and then use that acces token to access the protected endpoints in our API. However, this workflow is a bit tedious, and we have to copy-paste the access token into every request. Luckily, Insomnia has a feature called [request chaining](https://support.insomnia.rest/article/26-request-chaining) that allows us to simplify this workflow!

		## How to use request chaining with Insomnia

		Instead of passing the JWT in every request, you can access the `Headers` section and follow these steps. In the `Authorization` field, type `Bearer` add a space and then press `CTRL + SPACE` to get a contextual menu. Navigate to the `Response -> Body Attribute` field and select it, as shown in the screenshot below:

		![Contextual menu with Generator Tag options](./assets/bearer_token.png)

		After you've selected it, you'll see an error that looks like this:

		![Response error in the Authorization field](./assets/error.png)

		If you click on the error, you'll see a modal window:

		![Modal window with empty fields](./assets/modal.png)

		Inside of this window, you will first need to select a request that you want to get the data from. Click on `Select item` inside the `Request` field and choose the `POST /login` endpoint. After you've done that, go to the `Filter` field. In this field, we are telling Insomnia which part of the response we want to get from it. The prompt is started with the dollar sign `$` and then we can use the dot to access the attributes of the response. If we only type `$` or `$.`, we'll get a list of all the attributes of the response:

		![Attributes recieved from request using a dollar sign](./assets/attributes.png)

		In our case, we want to get the `access_token` attribute from the response, so we type `$.access_token`. If there was something else inside the `access_token` that you wanted to access like some value for example, you could do `$.access_token.value` and so on. After you've added the filter, you can set the `Trigger Behavior`. For example, you can set it to `When expired` and set time to 300 seconds. This means that the token will be refreshed every 5 minutes. The filled out window should look like this:

		![Filled out modal window with attributes recieved from request using a dollar sign followed by .access_token](./assets/filled_out.png)

		You can now press `Done` and you'll see that the error is gone and that the `Authorization` field is filled out with the `Bearer` token:

		![Filled out Authorization field with Bearer token](./assets/token.png)

		Since we use multiple protected endpoints, we would need to use the same method to get the `access_token` for every request. To tackle this problem, we can use [environment variables](https://support.insomnia.rest/article/13-environment-variables), as we did before for the `url` variable.

		To do this, you need to create a new environment variable. Click on the `No Environment` button in the top left corner of the Insomnia window and then click on the `Manage Environments` button, you will see a base environment that looks like this:

		![Base environment with url environment variable only](./assets/base_environment.png)

		Add a new environment variable called `access_token`, and for its value you should follow the same process from above. As a quick reminder, you should press `CTRL + SPACE` to get the contextual menu and then select the `Response -> Body Attribute` field. Click on the error that will show up and fill out the modal window as we've done before. Make sure to wrap the `Response -> Body Attribute` with quotation marks, as shown in the screenshot. When the variable is created, your environment should look like this:

		![Base environment with added access_token variable](./assets/environment.png)

		You will now be able to use this environment variable in all of the endpoints by simply writing `{{access_token}}` in the field that you want to use it in. Coming back to the first example, you can use the access token in the `Authorization` field by writing `Bearer {{access_token}}` and this will be the result:

		![Bearer with access_token environment variable](./assets/result.png)

		If you try and make the request, you will see that it works just like before, without needing to copy and paste the access token.