# Request {% hint style="info" %} Enables mocking, testing, and replaying {% endhint %} ## Fields
Hostname Name of the host where the request was received at
Port Port where the request received at
Path Request path e.g. /users/1
Latency Response latency in milliseconds
Status Response status code
## Components
Headers List of **name** and **value** pairs respectively representing the header name and header value
Query Params List of **name** and **value** pairs respectively representing the query param name and query param value
Body Data of blob format representing the request body
Response Represents a HTTP response. See details [here](/core-concepts/mock-api/requests/response.md)
Response Headers List of **name** and **value** pairs respectively representing the response header name and response header value
## Request Key Every request will have a unique identifier for your Stoobly context. This can be retrieved from the UI or the CLI. ### From the UI Navigate to the requests page then click on a request. This will open the request details page from the right side. At the top there will be a **Key** field which is the request Key.

Request Key in the details page

### From the CLI Run the following command to view some requests: ``` $ stoobly-agent request list method host path port body_text_hash query_params_hash body_params_hash committed_at latency query status is_deleted http_version key GET localhost /users 8081 cddd9a61a91320bb71702 287 200 0 1.1 eyJwIjogMCwgImkiOiA0MjR9 ``` Here in our example we have a single request. The request key can be found in the `key` column. In the example above, it is`eyJwIjogMCwgImkiOiA0MjR9`. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.stoobly.com/core-concepts/mock-api/requests.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.