Swiftpack.co -  gonzalezreal/SimpleNetworking as Swift Package
Swiftpack.co is a collection of thousands of indexed Swift packages. Search packages.
Scalable and composable API Clients using Swift Combine
.package(url: "https://github.com/gonzalezreal/SimpleNetworking.git", from: "2.0.0")


Twitter: @gonzalezreal

SimpleNetworking is a Swift Package that helps you create scalable API clients, simple and elegantly. It uses Combine to expose API responses, making it easy to compose and transform them.

It also includes other goodies, like logging and response stubbing.

Let's explore all the features using The Movie Database API as an example.

Configuring the API client

The APIClient is responsible for making requests to an API and handling its responses. To create an API client, you need to provide the base URL and, optionally, any additional parameters or headers that you would like to append to all requests, like an API key or an authorization header.

let tmdbClient = APIClient(
    baseURL: URL(string: "https://api.themoviedb.org/3")!,
    configuration: APIClientConfiguration(
        additionalParameters: [
            "api_key": "20495f041a8caac8752afc86",
            "language": "es",

Creating API requests

The APIRequest type contains all the data required to make an API request, as well as the logic to decode valid and error responses from the request's endpoint.

Before creating an API request, we need to model its valid and error responses, preferably as types conforming to Decodable.

Usually, an API defines different valid response models, depending on the request, but a single error response model for all the requests. In the case of The Movie Database API, error responses take the form of a Status value:

struct Status: Decodable {
    var code: Int
    var message: String

    enum CodingKeys: String, CodingKey {
        case code = "status_code"
        case message = "status_message"

Now, consider the GET /genre/movie/list API request. This request returns the official list of genres for movies. We could implement a GenreList type for its response:

struct Genre: Decodable {
    var id: Int
    var name: String

struct GenreList: Decodable {
    var genres: [Genre]

With these response models in place, we are ready to create the API request:

let movieGenresRequest = APIRequest<GenreList, Status>.get("/genre/movie/list")

But we can do better, and extend APIClient to provide a method to get the movie genres:

extension APIClient {
    func movieGenres() -> AnyPublisher<GenreList, APIClientError<Status>> {
        response(for: .get("/genre/movie/list"))

The response(for:) method takes an APIRequest and returns a publisher that wraps sending the request and decoding its response. We can implement all the API methods by relying on it:

extension APIClient {
    func createSession(with token: Token) -> AnyPublisher<Session, APIClientError<Status>> {
        response(for: .post("/authentication/session/new", body: token))
    func deleteSession(_ session: Session) -> AnyPublisher<Void, APIClientError<Status>> {
        response(for: .delete("/authentication/session", body: session))
    func popularMovies(page: Int) -> AnyPublisher<Page<Movie>, APIClientError<Status>> {
        response(for: .get("/movie/popular", parameters: ["page": page]))
    func topRatedMovies(page: Int) -> AnyPublisher<Page<Movie>, APIClientError<Status>> {
        response(for: .get("/movie/top_rated", parameters: ["page": page]))

Handling errors

Your app must be prepared to handle errors when working with an API client. SimpleNetworking provides APIClientError, which unifies URL loading errors, JSON decoding errors, and specific API error responses in a single generic type.

let cancellable = tmdbClient.movieGenres()
    .catch { error in
        switch error {
        case .loadingError(let loadingError):
            // Handle URL loading errors
        case .decodingError(let decodingError):
            // Handle JSON decoding errors
        case .apiError(let apiError):
            // Handle specific API errors
    .sink { movieGenres in
        // handle response

The generic APIError type provides access to the HTTP status code and the API error response.

Combining and transforming responses

Since our API client wraps responses in a Publisher, it is quite simple to combine responses and transform them for presentation.

Consider, for example, that we have to present a list of popular movies, including their title, genre, and cover. To build that list, we need to issue three different requests.

We could model an item in that list as follows:

struct MovieItem {
    var title: String
    var posterURL: URL?
    var genres: String
    init(movie: Movie, imageBaseURL: URL, movieGenres: GenreList) {
        self.title = movie.title
        self.posterURL = imageBaseURL
        self.genres = ...

To build the list, we can use the zip operator with the publishers returned by the API client.

func popularItems(page: Int) -> AnyPublisher<[MovieItem], APIClientError<Status>> {
    return Publishers.Zip3(
        tmdbClient.popularMovies(page: page)
    .map { (config, genres, page) -> [MovieItem] in
        let url = config.images.secureBaseURL
        return page.results.map {
            MovieItem(movie: $0, imageBaseURL: url, movieGenres: genres)

Logging requests and responses

Each APIClient instance logs requests and responses using a SwiftLog logger.

To see requests and responses logs as they happen, you need to specify the .debug log-level when constructing the APIClient.

let tmdbClient = APIClient(
    baseURL: URL(string: "https://api.themoviedb.org/3")!,
    configuration: APIClientConfiguration(
    logLevel: .debug

SimpleNetworking formats the headers and JSON responses, producing structured and readable logs. Here is an example of the output produced by a GET /genre/movie/list request:

2019-12-15T17:18:47+0100 debug: [REQUEST] GET https://api.themoviedb.org/3/genre/movie/list?language=en
├─ Headers
│ Accept: application/json
2019-12-15T17:18:47+0100 debug: [RESPONSE] 200 https://api.themoviedb.org/3/genre/movie/list?language=en
├─ Headers
│ access-control-expose-headers: ETag, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, Retry-After, Content-Length, Content-Range
│ Content-Type: application/json;charset=utf-8
│ x-ratelimit-reset: 1576426582
│ Server: openresty
│ Etag: "df2617d2ab5d0c85ceff5098b8ab70c4"
│ Cache-Control: public, max-age=28800
│ access-control-allow-methods: GET, HEAD, POST, PUT, DELETE, OPTIONS
│ Access-Control-Allow-Origin: *
│ Date: Sun, 15 Dec 2019 16:16:14 GMT
│ x-ratelimit-remaining: 39
│ Content-Length: 547
│ x-ratelimit-limit: 40
├─ Content
   "genres" : [
       "id" : 28,
       "name" : "Action"
       "id" : 12,
       "name" : "Adventure"

Stubbing responses for API requests

Stubbing responses can be useful when writing UI or integration tests to avoid depending on network reachability.

For this task, SimpleNetworking provides HTTPStubProtocol, a URLProtocol subclass that allows stubbing responses for specific API or URL requests.

You can stub any Encodable value as a valid response for an API request:

try HTTPStubProtocol.stub(
    User(name: "gonzalezreal"),
    statusCode: 200,
    for: APIRequest<User, Error>.get(
        headers: [.authorization: "Bearer 3xpo"],
        parameters: ["api_key": "a9a5aac8752afc86"]
    baseURL: URL(string: "https://example.com/api")!

Or as an error response for the same API request:

try HTTPStubProtocol.stub(
    Error(message: "The resource you requested could not be found."),
    statusCode: 404,
    for: APIRequest<User, Error>.get(
        headers: [.authorization: "Bearer 3xpo"],
        parameters: ["api_key": "a9a5aac8752afc86"]
    baseURL: URL(string: "https://example.com/api")!

To use stubbed responses, you need to pass URLSession.stubbed as a parameter when creating an APIClient instance:

let apiClient = APIClient(
    baseURL: URL(string: "https://example.com/api")!,
    configuration: configuration,
    session: .stubbed


Using the Swift Package Manager

Add SimpleNetworking as a dependency to your Package.swift file. For more information, see the Swift Package Manager documentation.

.package(url: "https://github.com/gonzalezreal/SimpleNetworking", from: "2.0.0")

Related projects

  • NetworkImage, a Swift µpackage that provides image downloading and caching for your apps. It leverages the foundation URLCache, providing persistent and in-memory caches.

Help & Feedback

  • Open an issue if you need help, if you found a bug, or if you want to discuss a feature request.
  • Open a PR if you want to make some change to SimpleNetworking.
  • Contact @gonzalezreal on Twitter.


Stars: 40
Last commit: 1 week ago

Ad: Job Offers

iOS Software Engineer @ Perry Street Software
Perry Street Software is Jack’d and SCRUFF. We are two of the world’s largest gay, bi, trans and queer social dating apps on iOS and Android. Our brands reach more than 20 million members worldwide so members can connect, meet and express themselves on a platform that prioritizes privacy and security. We invest heavily into SwiftUI and using Swift Packages to modularize the codebase.

Release Notes

SimpleNetworking 2.0.0
41 weeks ago

This release contains significant improvements and breaking changes:

  • Relax deployment target and use @available attribute where needed (#12).
  • Remove deprecated image loading code (#12).
  • Unified error handling and error response decoding (#13).
  • Rename Endpoint to APIRequest, for the sake of consistency (#15).
  • Add convenience factory methods for GET, POST, PUT, PATCH and DELETE requests (#17).
  • Better API for stubbing response (#18).
  • Write documentation for all the public types in the library (#16) and update the README (#19).

Swiftpack is being maintained by Petr Pavlik | @ptrpavlik | @swiftpackco | API