Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Posting review

Free#29 of 38 in API Clients

A focused terminal API client for keyboard-driven HTTP workflows.

6.2/10Editor score
Posting6.2 Visit Posting

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Posting is an open-source API client for creating, sending, inspecting, saving, and organizing HTTP requests from a terminal interface. Its keyboard-centric design includes jump mode, configurable keybindings, custom themes, and integrations with an external editor and pager. Collections are stored as readable YAML files, making the product a strong fit for developers who prefer local files, terminal workflows, and version-control-friendly API work across Windows, macOS, and Linux.

The workflow extends beyond basic request sending. Posting can load environment variables from one or more dotenv files and supports Python setup, pre-request, and post-response scripting. It imports cURL commands, OpenAPI 3.x specifications, and Postman collections, then exports requests to cURL. These capabilities make it practical for moving existing HTTP work into a terminal-based client, while local and SSH use also suit remote machines, containers, and Raspberry Pi devices. Choose Posting when keyboard control, portable collections, and scripting matter more than a browser-led interface.

Posting has a focused scope rather than a broad API collaboration platform. The published feature set does not include WebSocket support or automated tests, and team workspaces are not part of the described workflow. The roadmap identifies WebSocket/SSE support and a test framework as planned, while GraphQL and gRPC workflows are not part of the verified feature set. Posting is therefore a good choice for individual developers and teams comfortable managing readable local collections, but an alternative is more suitable when real-time protocols, built-in test automation, or shared team workspaces are central requirements.

Posting pros and cons

  • Where it wins
    • Readable YAML collections support version control.
    • Python scripting, dotenv environments, and cURL workflows.
    • Runs on Windows, macOS, Linux, SSH, containers, and Raspberry Pi.
  • Where it doesn't
    • No WebSocket support.
    • No automated testing framework.
    • No team workspaces or GraphQL workflow verified.

Posting fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update