Swiftpack.co - Package - Alamofire/Alamofire

Alamofire: Elegant Networking in Swift

Build Status CocoaPods Compatible Carthage Compatible Platform Twitter Gitter

Alamofire is an HTTP networking library written in Swift.


  • [x] Chainable Request / Response Methods
  • [x] URL / JSON / plist Parameter Encoding
  • [x] Upload File / Data / Stream / MultipartFormData
  • [x] Download File using Request or Resume Data
  • [x] Authentication with URLCredential
  • [x] HTTP Response Validation
  • [x] Upload and Download Progress Closures with Progress
  • [x] cURL Command Output
  • [x] Dynamically Adapt and Retry Requests
  • [x] TLS Certificate and Public Key Pinning
  • [x] Network Reachability
  • [x] Comprehensive Unit and Integration Test Coverage
  • [x] Complete Documentation

Component Libraries

In order to keep Alamofire focused specifically on core networking implementations, additional component libraries have been created by the Alamofire Software Foundation to bring additional functionality to the Alamofire ecosystem.

  • AlamofireImage - An image library including image response serializers, UIImage and UIImageView extensions, custom image filters, an auto-purging in-memory cache and a priority-based image downloading system.
  • AlamofireNetworkActivityIndicator - Controls the visibility of the network activity indicator on iOS using Alamofire. It contains configurable delay timers to help mitigate flicker and can support URLSession instances not managed by Alamofire.


  • iOS 8.0+ / macOS 10.10+ / tvOS 9.0+ / watchOS 2.0+
  • Xcode 8.3+
  • Swift 3.1+

Migration Guides


  • If you need help, use Stack Overflow. (Tag 'alamofire')
  • If you'd like to ask a general question, use Stack Overflow.
  • If you found a bug, open an issue.
  • If you have a feature request, open an issue.
  • If you want to contribute, submit a pull request.



CocoaPods is a dependency manager for Cocoa projects. You can install it with the following command:

$ gem install cocoapods

CocoaPods 1.1+ is required to build Alamofire 4.0+.

To integrate Alamofire into your Xcode project using CocoaPods, specify it in your Podfile:

source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '10.0'

target '<Your Target Name>' do
    pod 'Alamofire', '~> 4.6'

Then, run the following command:

$ pod install


Carthage is a decentralized dependency manager that builds your dependencies and provides you with binary frameworks.

You can install Carthage with Homebrew using the following command:

$ brew update
$ brew install carthage

To integrate Alamofire into your Xcode project using Carthage, specify it in your Cartfile:

github "Alamofire/Alamofire" ~> 4.6

Run carthage update to build the framework and drag the built Alamofire.framework into your Xcode project.

Swift Package Manager

The Swift Package Manager is a tool for automating the distribution of Swift code and is integrated into the swift compiler. It is in early development, but Alamofire does support its use on supported platforms.

Once you have your Swift package set up, adding Alamofire as a dependency is as easy as adding it to the dependencies value of your Package.swift.

Swift 3

dependencies: [
    .Package(url: "https://github.com/Alamofire/Alamofire.git", majorVersion: 4)

Swift 4

dependencies: [
    .package(url: "https://github.com/Alamofire/Alamofire.git", from: "4.0.0")


If you prefer not to use any of the aforementioned dependency managers, you can integrate Alamofire into your project manually.

Embedded Framework

  • Open up Terminal, cd into your top-level project directory, and run the following command "if" your project is not initialized as a git repository:

    $ git init
  • Add Alamofire as a git submodule by running the following command:

    $ git submodule add https://github.com/Alamofire/Alamofire.git
  • Open the new Alamofire folder, and drag the Alamofire.xcodeproj into the Project Navigator of your application's Xcode project.

    It should appear nested underneath your application's blue project icon. Whether it is above or below all the other Xcode groups does not matter.

  • Select the Alamofire.xcodeproj in the Project Navigator and verify the deployment target matches that of your application target.

  • Next, select your application project in the Project Navigator (blue project icon) to navigate to the target configuration window and select the application target under the "Targets" heading in the sidebar.

  • In the tab bar at the top of that window, open the "General" panel.

  • Click on the + button under the "Embedded Binaries" section.

  • You will see two different Alamofire.xcodeproj folders each with two different versions of the Alamofire.framework nested inside a Products folder.

    It does not matter which Products folder you choose from, but it does matter whether you choose the top or bottom Alamofire.framework.

  • Select the top Alamofire.framework for iOS and the bottom one for OS X.

    You can verify which one you selected by inspecting the build log for your project. The build target for Alamofire will be listed as either Alamofire iOS, Alamofire macOS, Alamofire tvOS or Alamofire watchOS.

  • And that's it!

    The Alamofire.framework is automagically added as a target dependency, linked framework and embedded framework in a copy files build phase which is all you need to build on the simulator and a device.

Open Radars

The following radars have some effect on the current implementation of Alamofire.

  • rdar://21349340 - Compiler throwing warning due to toll-free bridging issue in test case
  • rdar://26870455 - Background URL Session Configurations do not work in the simulator
  • rdar://26849668 - Some URLProtocol APIs do not properly handle URLRequest
  • rdar://36082113 - URLSessionTaskMetrics failing to link on watchOS 3.0+

Resolved Radars

The following radars have been resolved over time after being filed against the Alamofire project.

  • rdar://26761490 - Swift string interpolation causing memory leak with common usage (Resolved on 9/1/17 in Xcode 9 beta 6).


What's the origin of the name Alamofire?

Alamofire is named after the Alamo Fire flower, a hybrid variant of the Bluebonnet, the official state flower of Texas.

What logic belongs in a Router vs. a Request Adapter?

Simple, static data such as paths, parameters and common headers belong in the Router. Dynamic data such as an Authorization header whose value can changed based on an authentication system belongs in a RequestAdapter.

The reason the dynamic data MUST be placed into the RequestAdapter is to support retry operations. When a Request is retried, the original request is not rebuilt meaning the Router will not be called again. The RequestAdapter is called again allowing the dynamic data to be updated on the original request before retrying the Request.


Alamofire is owned and maintained by the Alamofire Software Foundation. You can follow them on Twitter at @AlamofireSF for project updates and releases.

Security Disclosure

If you believe you have identified a security vulnerability with Alamofire, you should report it as soon as possible via email to security@alamofire.org. Please do not post it to a public issue tracker.


The ASF is looking to raise money to officially register as a federal non-profit organization. Registering will allow us members to gain some legal protections and also allow us to put donations to use, tax free. Donating to the ASF will enable us to:

  • Pay our legal fees to register as a federal non-profit organization
  • Pay our yearly legal fees to keep the non-profit in good status
  • Pay for our mail servers to help us stay on top of all questions and security issues
  • Potentially fund test servers to make it easier for us to test the edge cases
  • Potentially fund developers to work on one of our projects full-time

The community adoption of the ASF libraries has been amazing. We are greatly humbled by your enthusiasm around the projects, and want to continue to do everything we can to move the needle forward. With your continued support, the ASF will be able to improve its reach and also provide better legal safety for the core members. If you use any of our libraries for work, see if your employers would be interested in donating. Our initial goal is to raise $1000 to get all our legal ducks in a row and kickstart this campaign. Any amount you can donate today to help us reach our goal would be greatly appreciated.


Alamofire is released under the MIT license. See LICENSE for details.


Stars: 27002
Help us keep the lights on



4.6.0 - Dec 4, 2017

Released on 2017-12-3. All issues associated with this milestone can be found using this filter.


  • Error mapping functions to Response types.
  • Separation of Usage and Advanced Usage docs from README.



4.5.1 - Sep 6, 2017

Released on 2017-09-06. All issues associated with this milestone can be found using this filter.


  • GitHub templates for issues and pull requests.
  • Jazzy docs for the release to work with GitHub Pages.
  • Dash support for Jazzy docs.


  • The project to work with Xcode 9 beta 6 on Swift 3.2 and 4.0.
  • The Travis CI config to work with Xcode 9 beta 6.
  • The cURL representation logic to no longer force unwrap URLCredential values.
  • The radars section of the README to split out open vs. resolved radars.
  • The installation section of the README to use the current version.


  • Issue in TaskDelegate where task access was not thread safe.
  • Issue in AF 4 migration guide where supported iOS versions was incorrect.
  • Issue in README sample code where PNG representation API was incorrect.
  • Swift 3.2+ API warnings for substring APIs.

4.5.0 - Jun 17, 2017

All issues associated with this milestone can be found using this filter.


  • Missing @escaping annotation for session delegate closures.
  • New mapError, flatMapError, withValue, withError, ifSuccess, and ifFailure APIs to Result.


  • The Travis config file to Xcode 8.3.
  • Response serialization implementation to use separate internal variable.
  • SessionDelegate internal implementation by removing redundant optional unwrap.
  • The debugPrintable implementation of Request to use curl -v instead of curl -i to be more verbose.
  • The MultipartFormData contentType property to be mutable.
  • Travis CI yaml file to enable watchOS 3.2 builds.
  • Alamofire to build with Xcode 9 with Swift 3.2 and 4.0 in addition to Xcode 8.3 and Swift 3.1.



4.4.0 - Feb 26, 2017

All issues associated with this milestone can be found using this filter.


  • A new Alamofire/Alamofire Gitter channel and also added badge to the README.
  • Functional extensions for Result, Data and Download Response.


  • Typo in the README in the Swift Package Manager section.
  • Issue in the "Modifying the Session Configuration" example code of the README where the defaultHTTPHeaders property was called incorrectly.
  • Issue in the "Security" section of the README where some example code was outdated.
  • Issue in the README where the POST request with parameters example was using the wrong method.
  • Issue where taskDidComplete override closure was not calling task delegate leading to potential memory leaks.

4.3.0 - Jan 16, 2017

All issues associated with this milestone can be found using this filter.


  • The host and path to router example in README.
  • A macOS disclaimer to download request example in README.
  • New value and error computed properties to data and download responses.
  • The HTTP method to the data and download response debug descriptions.
  • A README entry about installing through SPM.
  • The dependencies parameter to Package file for SPM since it's now required.
  • TLS evaluation tests for revoked certs for no policy and default policy.
  • New server trust policy for revoked certificates along with matching tests.


  • Project to Xcode 8.2 recommend settings.
  • The NetworkReachabilityManager to have a public instead of open ACL.
  • The initializers for both default responses public and added metrics parameter.
  • Internals by replacing syncResult extension with DispatchQueue sync.
  • TLS tests for tvOS 10.1 and added expiration test for revoked evaluation.


  • DownloadRequest sample code issue in AF 4 migration guide.
  • URLConvertible compiler issue in the README example.
  • An invalid comment in AF 4 migration guide.
  • An issue where the SessionManager did not respect retry time delay.
  • A broken reference link in the README.
  • Compiler issues in RequestAdapter and RequestRetrier examples in README.