You need need to ensure the {{postman_api_key}} variable is set correctly. (I lost count of the number of times I forgot to select the environment when submitting the final request).
You can ignore the GET and POST requests in the other folder, as they are not related to the authorization of the submit request.
You do not need to change the authorization settings at the collection or request level.
That should just be set to inherit from parent. So please set it back to that.
Please look at the screenshot I included previously. This is a screenshot of the submit collection request that is unaltered. It shows you that by default the x-api-key is already included, and is looking for a variable called postman_api_key.
When you highlight the variable in the headers tab of the submit request, it should show the current value (similar to what its doing in the authorization screen shot youâve included).
It looks like in the initial value you have the variable name posted instead of an actual value which wouldnât have worked. Basically, the variable calling itself. Instead of the value.
You donât really need to worry about the initial value. Itâs the current value that is important. It should a valid API key and should be in the format PMAK-xxxxxxxxxxxxx.
You havenât included enough of the screenshot for me to tell if youâve selected the environment from the drop down which is where I suspect the problem lies.
TLDR: You need to check your environment for a variable called postman_api_key and then ensure that the environment is selected before submitting the request. The current value needs to have your API key which should be in the format PMAK-xxxx. Thatâs all you should really need to do.
What I donât quite understand is that youâve had to do this when submitting the previous requests. So the process should be familiar by challenge # 9.