Open Source Swift HTTP Servers

Alamofire is an elegant, open source HTTP networking library written in Swift. It gives you an elegant interface on top of Apple’s URL loading system provided by the Foundation framework. It wraps the URLSession API among others in an easy-to-use interface and provides additional functionality required of modern application development using HTTP networking. Alamofire offers plenty of features, including Chainable Request / Response Methods, URL / JSON Parameter Encoding, Authentication with URLCredential, and HTTP Response Validation. Additional component libraries by the Alamofire Software Foundation also bring additional functionality to the Alamofire ecosystem.

Networking brings together URLSession, async-await (or Combine ), Decodable and Generics to simplify connecting to a JSON API. By providing a lightweight client that automates boilerplate code everyone has to write. By exposing a delightfully simple API to get the job done simply, clearly, and quickly. Getting swift models from a JSON API is now a problem of the past.

SwiftNIO is a cross-platform asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. Low-level protocol implementations are often a collection of ChannelHandlers that implement a protocol but still require the user to have a good understanding of SwiftNIO. Often, low-level protocol implementations will then be wrapped in high-level libraries with a nicer, more user-friendly API. High-level implementations are usually libraries that come with an API that doesn't expose SwiftNIO's ChannelPipeline and can therefore be used with very little (or no) SwiftNIO-specific knowledge. The implementations listed below do still do all of their I/O in SwiftNIO and integrate really well with the SwiftNIO ecosystem. SwiftNIO aims to support all of the platforms where Swift is supported. Currently, it is developed and tested on macOS and Linux.

Swift OpenAPI Generator is a Swift Package plugin that reads an OpenAPI document (YAML/JSON) and emits strongly typed client and server code. It removes boilerplate around request/response wiring so you focus on business logic while keeping strict type safety. The generated code uses a separate runtime package with pluggable transports and middlewares, enabling you to swap HTTP stacks or add cross-cutting concerns without touching the API layer. Swift-idiomatic naming and code structure in outputs. The project tracks ergonomic details like Swift casing conventions for generated types and properties. Releases provide a predictable upgrade path as the generator/runtimes evolve. Together, the plugin and runtime form a standardized pipeline from OpenAPI to production-ready Swift code.

Tiny http server engine written in Swift programming language. Lands on CocoaPods and others. Supports the latest non-beta Xcode and SPM. Stable. Stable branch plus experimental web-framework layer. Next version of Swifter (async IO).

Just is a client-side HTTP library inspired by python-requests, HTTP for Humans. URL queries, custom headers, form, JSON HTTP body. Redirect control. Multipart file upload along with form values. Basic/digest authentication, cookies, timeouts. Synchronous/asynchronous requests. Upload/download progress tracking for asynchronous requests. Link headers and friendly accessible results.

Pitaya is a Swift HTTP / HTTPS networking library for people. Inspired by Alamofire and JustHTTP. Carthage is a decentralized dependency manager that automates the process of adding frameworks to your Cocoa application.

Declarative HTTP networking, designed for SwiftUI. swift-request can be installed via the Swift Package Manager. Once you've built your Request, you can specify the response handlers you want to use. .onData, .onString, .onJson, and .onError are available. You can chain them together to handle multiple response types, as they return a modified version of the Request. The body of the Request is built using the RequestBuilder @resultBuilder. It merges each RequestParam in the body into one CombinedParam object. This contains all the other params as children. When you run .call(), the children are filtered to find the Url, and any other optional parameters that may have been included.