Access Adzerk's ad serving APIs via iOS
Swift Objective-C Ruby Shell
Latest commit e2c52d2 Dec 22, 2016 @subdigital subdigital update podspec version
Failed to load latest commit information.
SampleApp Update w/ latest Xcode/swift project settings Dec 21, 2016



Use of the Adzerk iOS SDK requires iOS 8.0 or later.


Installation of the framework can be done manually by building and copying the framework into your project, or with automatically with Carthage or CocoaPods.

Note that for manual and Carthage framework imports you may have to specify "Embedded Content Contains Swift Code" to avoid getting a linker error during build. Another way to force Xcode to load the Swift libraries is to add a single Swift source file to your project.


If you're using Carthage, add this to your Cartfile:

github "adzerk/adzerk-ios-sdk" ~> 1.0

If you want to be on the bleeding edge, you can specify the master branch:

github "adzerk/adzerk-ios-sdk" "master"

Then run carthage update to fetch and build the framework. You can find the framework in the Carthage folder, and you can add this to your project manually.


If you're using CocoaPods, add this to your Podfile:

pod 'adzerk-ios-sdk', '~> 1.0'

Again, if you want to be on the latest master branch:


pod 'adzerk-ios-sdk', github: 'adzerk/adzerk-ios-sdk', branch: 'master'

Then run pod install to download the code and integrate it into your project. You'll then open the pod-created workspace instead of your project to build.


All API operations are done with an instance of AdzerkSDK.

For most uses, a single Network ID and Site ID will be used for the entire application. If this is the case you can configure it once in the AppDelegate:

@import AdzerkSDK

func applicationDidFinishLaunching(...) {
  AdzerkSDK.defaultNetworkId = YOUR_NETWORK_ID
  AdzerkSDK.defaultSiteId = YOUR_SITE_ID

For requests that need a different Network ID or Site ID, you can specify this on the individual placement request.

Requesting Placements

To request a placement, you can build an instance of ADZPlacement and specify the attributes you want to send:

// Assumes that the default network ID and site ID are already set on AdzerkSDK
var placement = ADZPlacement(divName: "div1", adTypes: [1])!
placement.zoneIds = [3, 4, 5]

sdk.requestPlacements([placement]) { response in
  // handle response

Handling the Response

A placement request will accept a completion block that is handed an instance of ADZResponse. This is a Swift enum that will indicate success or failure.

sdk.requestPlacements([placement]) { response in
  switch response {
    case .Success(let placements): // ...
    case .BadRequest(let httpStatusCode, let responseBody): //...
    case .BadResponse(let responseBody): //...
    case .Error(let error): //..

Handle each case as appropriate for your application. In the case of .Success you are given an ADZPlacementResponse that contains the decisions for each placement requested.

A Note About Objective-C

Objective-C does not support Swift Enums, so an alternative callback-based method is provided. If you're using this SDK from and Objective-C project, you can request placements like this:

ADZPlacement *placement = [[ADZPlacement alloc] initWithDivName:@"div1" adTypes:@[@5]];
placement.zoneIds = @[@1];

AdzerkSDK *sdk = [[AdzerkSDK alloc] init];
[sdk requestPlacements:@[placement] options:nil success: ^void(ADZPlacementResponse *response) {
    NSLog(@"Response: %@", response);
} failure: ^void(NSInteger statusCode, NSString *body, NSError *error) {
    NSLog(@"  Status Code: %d", statusCode);
    NSLog(@"  Response Body: %@", body);
    NSLog(@"  Error: %@", error);

iOS 9 App Transport Security

If you're building for iOS 9, you'll notice that requests fail unless you configure your Info.plist properly. Our team is currently working to upgrade our servers to avoid this configuration in the future. In the meantime, you'll need to add the following exceptions for

  • NSExceptionMinimumTLSVersion to TLSv1.0
  • NSExceptionRequiresForwardSecrecy to NO

For more information on App Transport Security, see Apple's Tech Note. For a live example, see the sample project's Info.plist.

Building / Running Tests

Use Xcode 7.0 or later. Ensure that command line tools are installed:

xcode-select --install

xctool is used to build from the command line and give pretty output. Install it with homebrew:

brew install xctool

You can build and run tests with the provided build script:


Generating Docs

Docs are generated with jazzy and are hosted on github pages. To install jazzy:

$ gem install jazzy

If you're using system ruby, you'll probably need to prefix the above with sudo.

All doc generation happens on a different detached branch. Make sure your working copy is clean, close Xcode, and switch to the gh-pages branch:

$ git checkout gh-pages

Once there the content of the working directory becomes the static HTML site. Run the script to copy the latest version of the project from the master branch and run jazzy on it to generate the doc HTML:

$ ./

Once done, commit changes and push to github:

$ git add .
$ git commit -m "Update docs"
$ git push

After a few seconds, your changes will be live on


This SDK is released under the Apache 2.0 license. See LICENSE for more information.


  • 1.0: Swift 3 support

Breaking change: The Objective-C status code was changed from NSNumber * to NSInteger, as Swift 3 no longer automatically maps Int? to NSNumber *.

  • 0.4: Initial release