reqit 2.6.0: every request leaves a signed receipt
Ever tried to answer “what exactly did we send?” a day after an incident? Usually it is memory, a screenshot, and a token that has since rotated.
reqit 2.6.0 changes that. Every execution now writes a run receipt to .reqit/runs/.
A receipt records:
the request as written, with {{variables}} intact
where each variable came from — never its value
response status, safe headers, timing, and a SHA-256 of the body
a hash link to the previous receipt
an HMAC-SHA256 signature keyed from your OS keychain
Redaction happens before anything reaches disk: query values outside a safe allowlist, credential-shaped path segments and unknown header values are masked. Bodies are stored as hashes, not content. You can attach a receipt to a ticket or commit it without a secret sweep.
Verify anytime:
reqit runs verify
✓ 128 receipts verified — hashes and chain intact
Or open Trust → Run receipts in the desktop app for the same history in a UI.
What it is not: tamper-proof. It is tamper-evident — editing a receipt breaks the chain, and recomputing the chain still fails the signature without your key. Redaction is defense in depth, and recording stays best-effort so it can never fail a request. Those limits are documented.
Changelog: github.com/HalxDocs/reqit/bl…
Release: github.com/HalxDocs/reqit/re…
Shipped in 59 commits, with signed receipts across the app, CLI, runner, scheduler, MCP server and event replay.
Here is a blog on it
Enjoy.
halxdocs.com/blog/signed-run…
reqit 2.6.0: every request leaves a signed receipt
Ever tried to answer “what exactly did we send?” a day after an incident? Usually it is memory, a screenshot, and a token that has since rotated.
reqit 2.6.0 changes that. Every execution now writes a run receipt to .reqit/runs/.
A receipt records:
the request as written, with {{variables}} intact
where each variable came from — never its value
response status, safe headers, timing, and a SHA-256 of the body
a hash link to the previous receipt
an HMAC-SHA256 signature keyed from your OS keychain
Redaction happens before anything reaches disk: query values outside a safe allowlist, credential-shaped path segments and unknown header values are masked. Bodies are stored as hashes, not content. You can attach a receipt to a ticket or commit it without a secret sweep.
Verify anytime:
reqit runs verify
✓ 128 receipts verified — hashes and chain intact
Or open Trust → Run receipts in the desktop app for the same history in a UI.
What it is not: tamper-proof. It is tamper-evident — editing a receipt breaks the chain, and recomputing the chain still fails the signature without your key. Redaction is defense in depth, and recording stays best-effort so it can never fail a request. Those limits are documented.
Changelog: github.com/HalxDocs/reqit/bl…
Release: github.com/HalxDocs/reqit/re…
Shipped in 59 commits, with signed receipts across the app, CLI, runner, scheduler, MCP server and event replay.
Reqit v2.5.0 is out 🚀
New: Vault refs, mock server rules, encrypted environments, and backup health.
Also fixed macOS updates, editor shortcuts, timing precision, and more.
📦 github.com/HalxDocs/reqit/re…
Thanks to everyone reporting issues!
Reqit just crossed 700+ downloads and 70 stars.
Built as a local-first, Git-native API client. No cloud, no account, just your APIs and your workflow.
Appreciate everyone supporting it. More to come.
reqit.dev
Reqit retweeted
🛠 Developer Tools:
TypeBridge (@Ironali_)
FORX (@ezekielreu6)
Gigscout (@MayowaSWE)
@pxxl_space
@senviok
@roles_tab
@GO54_hq
@_reqit
@buildwchavica
@brimblehq
I see @_reqit
Hey guys, today I finished building batch email sending for Sendlib. You can now send one request to our batch endpoint with hundreds of recipients.
Sendlib handles the background queue, Gmail rate limits, and exponential backoff automatically, so you don't have to build that infrastructure yourself.
Once you create a batch, we instantly give you a batchId that you can use to monitor its status and track how many emails have been sent or failed through our API. You can also personalize each email using variables like {{name}} and {{company}}. Batch sending is currently available on the Pro plan.
Check it out: sendlib.samueltuoyo.com/docs…
Reqit retweeted
WEEK #7 of listing startups on @afro_launch - a platform that helps African startups get discovered.
These startups are already on the leaderboard for this week:
• @join_huxxle
• @_reqit
• @seamless_hr
• @GO54_hq
• @Jobbermandotcom
• @wearekudilo
• Edumawu
🌍 Only 04h 57m 55s left to vote for your favourite African startups!
Cast your vote now on Afrolaunch → afrolaunch.com
We heard you.
Coming soon to reqit: real-time APIs that actually work
We heard you — gRPC, SSE, and WebSockets haven't been reliable. Here's what we're fixing:
SSE
- Streams no longer cut off after 30 seconds
- Reconnects on its own and remembers where it left off (Last-Event-ID)
- Big messages won't get cut off anymore
WebSockets
- Now supports custom headers, cookies, and subprotocols — so more real servers will accept your connection
- Binary messages work correctly instead of showing up garbled
gRPC
- This is the big one: we're replacing the current workaround with a real gRPC client, so it will connect to actual gRPC servers
- Adds server reflection (drop in a URL, methods auto-load)
- Supports proto files, all streaming types (client, server, bidirectional), and canceling a call at any time
These fixes come in phases, starting with making the basics stable first. Thanks for your patience — more details and release notes as each phase ships.
1,202







