Get specific player

GET {{mock_url}}/player
RESPONSES

status: OK
&quot;{\n    \&quot;welcome\&quot;: \&quot;Welcome! Check out the &#39;data&#39; object below to see the values returned by the API. Click **Visualize** to see the &#39;tutorial&#39; data for this request in a more readable view.\&quot;,\n    \&quot;data\&quot;: {\n        \&quot;name\&quot;: \&quot;{{$randomFirstName}}\&quot;,\n        \&quot;played\&quot;: {{$randomInt}}\n    },\n    \&quot;tutorial\&quot;: {\n        \&quot;title\&quot;: \&quot;Pre-request scripts\&quot;,\n        \&quot;intro\&quot;: \&quot;Your request successfully specified a player to retrieve using their ID.\&quot;,\n        \&quot;steps\&quot;: [\n            {\n                \&quot;note\&quot;: \&quot;The request returned the following (random mock) data:\&quot;,\n                \&quot;ref_data\&quot;: \&quot;data\&quot;\n            },\n            {\n                \&quot;note\&quot;: \&quot;The way the request is set up now, the parameter only has a value after the first request runs, but we can also give it a default value when that hasn&#39;t happened. Temporarily deselect the environment, so that **No Environment** is selected in the drop-down list. In the request **Pre-request script** add the following code:\&quot;,\n                \&quot;js_code\&quot;: [\n                    \&quot;if(!pm.variables.get(&#39;player_id&#39;)) pm.variables.set(&#39;player_id&#39;, -1);\&quot;\n                ]\n            },\n            {\n                \&quot;note\&quot;: \&quot;It sets a default value of `-1` only if there is not a value set yet. Hover over the **Param**—the variable is unresolved. **Send** the request again and check the console to see that `-1` was sent.\&quot;,\n                \&quot;pic\&quot;: \&quot;https://assets.postman.com/postman-docs/student-expert-open-console-web.jpg\&quot;\n            },\n            {\n                \&quot;note\&quot;: \&quot;Select the environment you created again from the drop-down list and hover over the var again—now it should again have the value from the var you set from the first request.\&quot;\n            }\n        ],\n        \&quot;next\&quot;: [\n            {\n                \&quot;step\&quot;: \&quot;Before you continue with scripting, add a description to this request—the description will appear within the collection documentation, which you would use if you were e.g. publishing an API for public use. In the Postman app, click the Documentation icon in the far right menu of the request. Hover over the text body and click the pencil icon to enter edit mode. Add a short description of the request (you can use markdown) and click **Save**.\&quot;,\n                \&quot;pic\&quot;: \&quot;https://assets.postman.com/postman-docs/student-expert-add-description-web.jpg\&quot;\n            },\n            {\n                \&quot;step\&quot;: \&quot;You can view documentation inside each request individually, or see an overview of an entire collection&#39;s documentation by clicking the three dots next to a collection folder and selecting &#39;View documentation&#39;\&quot;\n            },\n            {\n                \&quot;step\&quot;: \&quot;Open the next request `Get stats` and click **Send**.\&quot;\n            }\n        ]\n    }\n}&quot;