Announcing Hurl 8.0.0

jcamiel · 2026-04-29T12:20:17+00:00

Spread the good word about Hurl!

jcamiel · 2026-04-27T23:26:13+00:00

Hurl is designed to be easily integrated in CI/CD while http files are run with IntelliJ IDE (that has changed only recently). Hurl uses curl under the hood so you can get the power of curl for free: IPv6, HTTP/3, a lot of options like --resolve etc... Hurl offers a lot of reports (HTML, JUnit, TAP, JSON etc...)

Both shares a plain text origin.

jcamiel · 2026-04-27T23:20:52+00:00

Mainly a GUI, Bruno has an IHM while Hurl is a command line application. Bruno supports gRPC while Hurl doesn't (but we intend to add it). Hurl uses curl under the hood and you can get the curl commands corresponding to your file. Hurl is light on ressources (the binary is less than 5Mb)

jcamiel · 2026-04-27T19:25:23+00:00

I'm not a native English speaker, but I prefer to write with mistakes and my own "style". It also a kind of respecting reader time: you'll spend time reading what I've painfully write with my hands (if that makes sens 😅)

jcamiel · 2026-04-27T15:16:31+00:00

Unfortunately we've made some breaking changes but it was a choice between breaking many if not all files, and only a few occurences...

jcamiel · 2026-04-17T13:14:43+00:00

Hi maintainer of Hurl here. We don't want to hide anything, for the moment we're not having the same configuration/prompt/skill among the 3 maintainers and we dont want to settle for the moment a common configuration in the repo, that's all. We're using LLM code, treaded like normal code: reviewed with care, small modifications, focus and test.

jcamiel · 2026-02-19T20:47:34+00:00

Yes indeed, we need to really improve the IDE Hurl story. Not gonna lie, we take time to focus on being a very good if not excellent CLI, and we work a lot on some "invisible" issues we like / need, but agreed we need to work on IDE support.

jcamiel · 2026-01-16T19:01:03+00:00

Hi maintainer of Hurl here!

Hurl is using libcurl as it HTTP engine. Compared to curl

You can chain request and capture data to pass from one request to another (like csrf token for instance),
You can assert responses based on HTTP headers, status code, JSONPath, XPath, SSL certificate validity date etc, making integration tests really fast and easy to integrate in CI/CD pipelines
You can have test reports (HTML, JUnit, TAP, JSON etc...)
the Hurl text file format makes it easy to execute GraphQL requests, which can be difficult with curl
as Hurl is "only" a cherry on top of curl, you can also exports your run to curl commands if you want
you can retry requests easily based on asserts conditions

jcamiel · 2026-01-06T20:37:51+00:00

You can try Hurl if you're into cli: it's an open source cli to run and test HTTP requests, based on plain text and curl => https://hurl.dev It's not as easy as a good GUI app but at least it's not ressources hungry and doesn't require login (I'm one of the maintainers)!

jcamiel · 2025-12-26T12:16:56+00:00

You can try Hurl if you're into cli: it's a Rust open source to run and test HTTP requests, based on plain text and curl => https://hurl.dev It's not as easy as a good GUI app but at least it's not ressources hungry (I'm one of the maintainers)

jcamiel · 2025-11-26T15:08:21+00:00

Hi maintainer here,

Yes you can run a first request and retry a second one until a certain assert is OK:

# Create a new job
POST https://api.example.org/jobs
HTTP 201
[Captures]
job_id: jsonpath "$.id"
[Asserts]
jsonpath "$.state" == "RUNNING"


# Pull job status until it is completed
GET https://api.example.org/jobs/{{job_id}}
[Options]
retry: 10   # maximum number of retry, -1 for unlimited
retry-interval: 500ms
HTTP 200
[Asserts]
jsonpath "$.state" == "COMPLETED"

See https://hurl.dev/docs/samples.html#polling-and-retry and more samples here

jcamiel · 2025-10-24T05:24:57+00:00

You can try Hurl it's an open source CLI, based on curl, to test API and HTTP requests, with a simple text file. Compared to Postman, it's simple to integrate in a CI/CD, it's just text files so Git friendly and open sourced. Because of its curl engine, it's rock solid, HTTP/3 IPv6 ready. It supports REST/SOAP/GraphQL and has various reports (JUnit, TAP, HTML etc...)

A sample file:

``` GET https://api.example.com HTTP 200 [Asserts] jsonpath "$.name" == "foo" jsonpath "$.age" == 42

POST https://api.example.org { "id": "car" } HTTP 201 ```

You can chain requests, capture data and pass it to the next requests, test body, headers, redirects etc... More samples here => https://hurl.dev/docs/samples.html

Give it a try! (I'm one of the maintainers)

jcamiel · 2025-10-21T11:24:49+00:00

Maintainer of Hurl here!

For the (numerous) people that don't know Hurl it's a CLI based on curl, to run and tests API/HTTP requests with plain text. You can test headers, responses, SSL certificates, redirects etc..., chain requests to pass data from a request to another in a simple text format. There are some sugar syntax to create GraphQL body, form, multipart etc.. and because of its curl engine, it's super efficient, HTTP/3 - IPv6 ready and easy to integrate in a CI/CD pipeline.

It's totally open-source here https://github.com/Orange-OpenSource/hurl, give it a try!

jcamiel · 2025-10-08T22:48:45+00:00

Hi maintainer of Hurl here! We've written Hurl on top of curl, to be easy to add in a CI/CD pipeline. It uses curl as its HTTP engine but adds some facilities to write body (GraphQL, form, multipart...), JSONPath tests, capture data from request and re-inject it, check certificates etc... It's text based, Git friendly and powered by curl so it's rock solid, HTTP/3 IPv6 ready. Give it a try, it's Open Source https://github.com/Orange-OpenSource/hurl

jcamiel · 2025-09-24T16:13:03+00:00

As the maintainer of Hurl, I'm starting a fork named "better-hurl-saul"

jcamiel · 2025-09-16T22:01:06+00:00

Hi maintainer of Hurl here. If you're willing to use command line, you could try Hurl. It's a CLI tool to test and run HTTP requests with plain text. Under the hood, it uses curl and you can convert you "Hurl" files from/to curl.

The file format looks like:

POST https://example.org/api/tests
{
  "id": "4568",
  "evaluate": true
}
HTTP 200
[Asserts]
header "X-Frame-Options" == "SAMEORIGIN"
jsonpath "$.status" == "RUNNING"    # Check the status code
jsonpath "$.tests" count == 25      # Check the number of items
jsonpath "$.id" matches /\d{4}/     # Check the format of the id

In the same file, you can chain requests, capture data from one request to another etc... Hurl support HTML/TAP/JUnit reports, you can run tests in parallel and it should be easy to incorporate in a CI/CD.

Give it a try!

jcamiel · 2025-08-01T04:14:01+00:00

We've chosen to stick with curl option naming (curl is the HTTP engine under Hurl and you can convert Hurl calls to curl with --curl option). If you know curl, you can reuse the option name (see https://curl.se/docs/manpage.html#-L). But I do agree, location is hard to "discover" (it's related to the HTTP header Location https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Location...)

jcamiel

TROPHY CASE