> For the complete documentation index, see [llms.txt](https://cbdebugger.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cbdebugger.ortusbooks.com/collectors/hyper-http-collector.md).

# Hyper HTTP Collector

Profile all calls made by Hyper as http/s

You can use the `hyper` configuration structure to configure the `hyper` panel in the debugger. This will track all outgoing http/s calls made by the Hyper module in your debugger.

<figure><img src="https://639975657-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkinv4fgugMReTxKWlgH5%2Fuploads%2FVpzre7dNFwboCN9HLZbj%2Fimage.png?alt=media&amp;token=9d9ff06e-12dc-4d9e-a421-c1fb178391f5" alt=""><figcaption><p>Hyper Panel</p></figcaption></figure>

{% hint style="info" %}
Hyper exists to provide a fluent builder experience for HTTP requests and responses. It also provides a powerful way to create clients, i.e. Builder objects with pre-configured defaults like a base URL or certain headers.

#### <https://forgebox.io/view/hyper> <a href="#requirements" id="requirements"></a>

{% endhint %}

```cfscript
// Hyper Collector
hyper    : {
	enabled         : false,
	expanded        : false,
	logResponseData : false,
	logRequestBody  : false
}
```

<table><thead><tr><th width="206">Key</th><th width="126">Type</th><th width="89">Default Value</th><th>Description</th></tr></thead><tbody><tr><td><code>enabled</code></td><td>Boolean</td><td>false</td><td>Enable the collector</td></tr><tr><td><code>expanded</code></td><td>Boolean</td><td>false</td><td>Expand the panel by default or not</td></tr><tr><td><code>logResponseData</code></td><td>Boolean</td><td>false</td><td>Log the response from the API Call</td></tr><tr><td><code>logRequestBody</code></td><td>Boolean</td><td>false</td><td>Logs the request body</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cbdebugger.ortusbooks.com/collectors/hyper-http-collector.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
