HTTP Libraries

sling1.7k★

If you write Go and make HTTP requests, Sling is a small library that makes building and sending those requests less tedious. Instead of manually constructing http.Request objects, setting headers, encoding query parameters, and parsing responses — Sling gives you a chainable builder pattern. Think of it as a Go equivalent of Python's requests library, but lighter. 1.7K stars, MIT license, Go. The API is clean: `sling.New().Base(url).Get(path).QueryStruct(params).ReceiveSuccess(response)`. Supports JSON encoding/decoding, form data, custom headers, and base URL composition. No external dependencies beyond the standard library. Fully free. It's a library — install it with `go get`, use it in your code. No service, no hosting, nothing to pay for. Any team writing Go HTTP clients: use it if you're tired of boilerplate. Solo to enterprise, the calculus is the same — it's a dependency that simplifies code. The catch: 1.7K stars and minimal velocity means this is a mature-but-quiet project. The Go standard library's `net/http` is already good — Sling saves typing but doesn't add capabilities. If your team has strong opinions about minimizing dependencies, the standard library does everything Sling does with more code. And for complex API clients, you might want a full SDK generator like OpenAPI instead of a request builder.