TReq

A Terminal Request HTTP Client.
TReq is a user-friendly Command Line Interface (CLI) HTTP client, designed to be simple and a complete CLI tool to interact with APIs
[!NOTE] TReq, short for Terminal Request, is a user-friendly Command Line Interface (CLI) HTTP client that goes beyond the stateless nature of typical CLI HTTP clients. It's designed to offer a complete tool for interacting with APIs in the terminal.
While traditional CLI HTTP clients excel at quick tasks and small tests, TReq aims to bridge the gap by introducing statefulness, allowing users to store, handle, edit, view, and inspect requests seamlessly, all within the terminal.
Inspired by HTTPie, TReq seeks to implement and extend its main features, making the experience of making HTTP calls in the terminal as simple as possible, without the need for extensive graphical tools.
Features
- Made to APIs and REST: TReq is tailored for working with APIs, REST, and JSON with minimal effort.
- HTTPie based: The CLI interface is entirely based on HTTPie, ensuring familiarity for existing users.
- Easy payload generation : Quickly declare fields for the payload with user-friendly syntax.
- Persistent Request Storage: Save and edit frequently used requests with simple commands. View details of stored requests.
- Pretty Outputs: The UX is relevant in a CLI.
Installation
Ubuntu / Debian based
Download the latest .deb package from the last release page. Open your terminal and navigate to the directory where the downloaded .deb file is located. Install TReq using the following command:
Alternatively, you can try:
Arch / Manjaro
If you're using Arch Linux, you can install TReq from the AUR using an AUR helper such as yay:
Cargo
For any OS, the best way to install TReq is using cargo.
Install cargo using rustup and then...
Linux generic
TReq's binary is statically linked and has no dependencies, making it compatible with most major Linux distributions. To install, download the binary from the latest release page and place it in your PATH directory.
Using Curl
Using wget
Windows
Download the latest .exe file at last release page. Place the downloaded .exe file in a directory included in your system's PATH, or add the directory containing the .exe to your PATH.
Usage
For more detailed information on commands and options, refer to the built-in help:
Basic requests
# GET requests
# Another methods...
# ...
Body, header e params manipulation
# POST with JSON payload => { "language": "Rust", "food": "pizza" }
# POST with custom Header => { Content-Type: application/json }
# Define query params at url
# (these two below are equivalent)
&job=dev
More complex requests
# POST with JSON payload
# => {
# "friends": ["John", "Jane"],
# "job": "dev",
# food": "pizza"
# }
# Same above request with also
# a custom Header
# and a query param at url (example.com?sort=true)
Managing saved requests
Saving requests
# After requesting you can save it
# Now you can execute the
Overwriting requests datas at running
# Before submit the same request you can edit specific fields and insert new datas
# Inserting a query param
# Inserting a header
# Then, save it as a new request
Localhost alias
When defining urls with localhost, you can use the alias :{PORT}/{ROUTES} instead of complete url.
For example, each pair of the commands below are equivalents...
Contributing
Contributions and feature requests are welcome! Feel free to submit issues or pull requests on our GitHub repository.
Upcoming features
- TUI view like https://github.com/talis-fb/legacy_treq
- Enviroment Variables in Request payloads (like {{ .env.ENV_NAME }})