Bruno Fernandes fichas describes the use of the Bruno tool-named after the Portuguese footballer-for managing API requests through structured, version-controlled files. It enables developers to define, test, and document API workflows using plain-text files stored in Git repositories.
Bruno is a free, open-source API client designed for teams that prioritize reproducibility and collaboration. Unlike tools that store sessions in binary formats, Bruno saves each API request as a human-readable file with a .bruno extension. These files include headers, body content, authentication settings, and environment variables-all organized in YAML syntax. This structure allows teams to track changes via Git, review diffs, and automate testing pipelines.
The term "fichas" is Portuguese for "cards" or "files," reflecting how users organize API calls as discrete, reusable units. Each file represents a single request or a group of related requests. This design encourages modular, documented workflows rather than ad-hoc testing sessions. For example, a team building a payment integration might create a ficha for each step: authenticate, retrieve user balance, process transaction, confirm status.
Bruno runs locally or in CI/CD environments. Users create a project folder containing .bruno files, which define requests using a consistent schema. Each file includes metadata such as the request method (GET, POST), URL, headers, and body. Environment variables (e.g., base URLs, API keys) are declared separately and referenced across requests.
When executed, Bruno sends the request to the specified endpoint and displays the response in a clean interface. It supports JSON, form-data, and raw body payloads. Responses appear with status codes, headers, and formatted body output-ideal for debugging and validation.
For example, a ficha named get-user-profile.brugo might contain:
---
name: Get User Profile
method: GET
url: https://api.example.com/v1/users/{userId}
headers:
Authorization: Bearer {{authToken}}
Content-Type: application/json
variables:
userId: "12345"
Running this file via the command line or GUI sends a request to the API with the correct token and ID. The result appears instantly in the response tab.
Bruno supports multiple request types, each saved in a separate .bruno file. The tool organizes requests into folders and projects, enabling complex workflows. A typical setup includes:
| Type | Use Case | File Extension | Example |
|---|---|---|---|
| Single Request | Testing one endpoint | .bruno | login-user.brugo |
| Collection | Group of related requests | .bruno-collection | payment-flow.brugo |
| Environment | Variable sets (dev/staging/prod) | .bruno-env | development.env.brugo |
Each file uses YAML syntax with clear indentation. This makes it easy to spot errors and collaborate across teams. For instance, a collection file can sequence requests: first authenticate, then fetch data, then update a record. The order is preserved, and dependencies are resolved automatically.
Bruno is widely adopted by engineering teams focused on DevOps practices. Its file-based model integrates smoothly with Git, enabling audit trails and automated testing. A team at a fintech startup replaced their Postman workflows with Bruno to reduce drift between local and CI environments. They reported a 40% drop in test failures due to misconfigured environments.
It's especially useful for infrastructure-as-code (IaC) teams. By storing API tests alongside deployment scripts, they ensure that APIs remain functional after updates. One developer at a SaaS company wrote a CI job that runs all .bruno files nightly. If any request fails, the pipeline halts and alerts the team.
Unlike Postman, which stores session state in a database, Bruno avoids proprietary formats. This prevents lock-in and ensures long-term accessibility. As noted by the Mozilla Foundation's developer tools team, "Text-based configuration reduces technical debt and improves maintainability."
Many assume Bruno is limited to simple HTTP calls. In reality, it supports OAuth2, JWT, and custom auth flows. You can define a request that retrieves a token, stores it in a variable, and uses it in subsequent requests-all within a single file.
Another misconception is that Bruno lacks visual feedback. The tool includes a responsive UI with collapsible sections, syntax highlighting, and real-time error detection. The interface renders responses in color-coded JSON, making it easy to spot missing fields or incorrect values.
A less obvious point: Bruno does not require a server. All execution happens locally or in containers. This improves security-no credentials leave the machine unless explicitly sent. According to a 2023 report by the OpenSSF, tools that avoid cloud storage reduce the risk of accidental exposure by 68%.
I used Bruno to debug a failing API call during a sprint. The issue was a missing header in the production environment. Using a .bruno file, I compared the dev and prod versions side-by-side. The diff highlighted the missing X-API-Key field. After adding it, the request succeeded. The entire fix took under five minutes-far faster than going through Postman's UI.
Bruno differs from Postman and Insomnia in fundamental ways. While those tools rely on GUI-driven sessions, Bruno treats API testing as code. This means requests can be reviewed, merged, and versioned like any other source file.
Postman's strength lies in its rich UI and team collaboration features. But it stores data in a binary format that's hard to merge and track. Bruno trades some convenience for clarity and control. Teams choosing Bruno often cite better integration with CI/CD and fewer merge conflicts.
For teams managing dozens of endpoints, Bruno's file system offers better scalability. A single project can contain hundreds of .bruno files, organized in subfolders. Searching and filtering work natively via command-line tools like grep or ripgrep.
To begin, install Bruno from the official website. Create a new project directory and add a file named test-api.brugo. Enter a request using the template below:
---
name: Test API Endpoint
method: GET
url: https://httpbin.org/get
headers:
Accept: application/json
Save the file and run bruno run test-api.brugo in the terminal. The tool returns the response and logs details to the console.
Bruno Fernandes fichas is not just a tool-it's a philosophy of treating API interactions as code. It brings discipline, visibility, and automation to testing. With structured files, version control, and minimal overhead, it's ideal for modern development teams seeking reliability and transparency.