Proposal: Sequential execution of multiple HTTPie requests via STDIN #1683

Checklist

• I've searched for similar feature requests.

Enhancement request

I’d like to propose an opt-in way to execute multiple HTTPie request definitions sequentially via STDIN, one request at a time, using a single HTTPie invocation.

This would allow users to pipe a stream of complete request definitions into HTTPie and have them executed in order, without introducing repetition, scheduling, concurrency, or automation workflows.

Problem it solves

I’m often debugging or exploring APIs that require multiple dependent steps, such as:

• authenticate → fetch resource → submit data
• create entity → verify → update → delete

Today, this requires chaining multiple http commands in shell scripts, which quickly becomes hard to read, reuse, or share.

I’m trying to define and execute a clear, human-readable sequence of HTTP requests so that multi-step API interactions can be explored and debugged more easily, without turning HTTPie into a load-testing or workflow tool.

Additional information, screenshots, or code examples

Example usage (illustrative)

cat requests.http | http --sequence

Where requests.http contains:

GET https://httpbin.org/get
POST https://httpbin.org/post name=alice
GET https://httpbin.org/headers

Notes on scope (explicit non-goals)

This proposal does NOT aim to support:

• request repetition or looping
• delays, timers, or scheduling
• concurrency or batching
• load testing or benchmarking

Each request would be executed once, strictly in order, with normal HTTPie output.

If this direction aligns with HTTPie’s scope, I’d be happy to work on an implementation and tests following existing CLI patterns.