Bruno: keep API request collections beside your code

Put request definitions under review

Bruno is a desktop API client by Anoop M D, Anusree P S and contributors. It stores collections in a local folder using the text-based Bru format, so request definitions can be reviewed alongside code in Git. Consider it when you want a collection you can inspect and version, rather than a history of one-off requests. The community source is MIT-licensed; additional commercial features have separate terms.

Start with one ordinary request

Create or open a collection you trust and choose the intended environment. Start with a read-only request to an API you are authorized to use. Inspect the URL, headers, status and response before adding scripts, imported collections or a runner. Keeping files locally does not mean requests never connect to servers, and a collection should not be assumed safe to commit with credentials inside it.

Do not assume examples inherit everything

The 4.3.0 release introduces a Try action for response examples. In issue 9759, Ronan-costa reports that on Windows this action omits a folder- or collection-level Bearer token, while the ordinary request works. The issue is open at the November 5 check and has no maintainer confirmation. This is one user's report, not a Boloop reproduction or proof that all authentication paths fail. If an example returns 401, compare its actual authorization behavior with the ordinary request before changing the API server's permissions.

Separate transport success from acceptance

An HTTP success status answers only part of a test. Check the expected response and, when relevant, read back the intended business state through an authorized route. The existing AI-generated code review and acceptance checklist provides a way to record the version, steps, expected result and evidence. This recommendation is based on official documentation and the linked independent report; Boloop has not benchmarked Bruno or tested an API with it.