Skip to main content
Request headers are key-value pairs sent along with an HTTP request to provide additional information to the server about the request. The request headers give the server more information about how to process the incoming request. Default Headers: Default headers are predefined headers that are part of the HTTP specification. Custom Headers: Custom headers are headers that are user-defined and are not part of the official HTTP specification.

​
Create request headers in Bruno

  1. Create request inside collection.
  2. Navigate to the Headers tab.
  3. Enter the Name, Value, and an optional Description for each header.
  4. Save and execute the request.
req-headers
To view default headers, navigate to the Headers tab in your request. For custom headers, check the Timeline tab.

​
Inherited headers

The Headers tab shows an Inherited Headers accordion listing headers coming from the collection, any parent folders, and Bruno’s runtime defaults. This lets you see exactly which headers will be sent with the request without opening collection or folder settings. Inherited rows are read-only and cannot be toggled from the request. Click a row’s source link to jump straight to the originating collection or folder row, which is scrolled into view and briefly highlighted. Precedence and visibility:
  • A header defined on the request overrides same-named inherited headers (case-insensitive) and hides them from the inherited list.
  • Among inherited headers, the nearest source wins: folder headers override collection headers of the same name.
  • Disabled inherited headers are ignored and are not sent.

​
Streaming with Server-Sent Events

To work with Server-Sent Events (SSE), set:
Bruno keeps the connection open, streams chunks into the response panel live, and swaps the Send button for Cancel while the stream is active. See Server-Sent Events (SSE) for details on cancellation, collection runs, and CLI behavior.