Tutorials

Getting Started with Contentful and Swift

This guide will show you how to get started using our Swift client library to consume content.

Contentful’s Content Delivery API (CDA) is a read-only API for retrieving content from Contentful. All content, both JSON and binary, is fetched from the server closest to a user’s location by using our global CDN.

We publish client libraries for various languages to make developing applications easier.

Requirements

This tutorial assumes that you understand the Contentful data model.

Authentication

For every request, clients need to provide an API key, which is created per space and used to delimit applications and content classes.

You can create an access token using the Contentful web app or the Content Management API.

Install the client library

There are different ways to integrate the client library into your own apps, described in detail in the README for the client library. This guide will use CocoaPods, the dependency manager for Cocoa projects, which helps you keep the client library up-to-date:

Create a Podfile for your project which adds Contentful as a dependency for you project. You can specify a particular version(s) of the client library using the various operators that Cocoapods offers

1use_frameworks!
2
3target 'Your Xcode targets name' do
4  pod 'Contentful'
5end

Initialize the client

You need an API key and a space ID to initialize a client. You can use the API key and space ID pre-filled below from our example space or replace them with your own values.

1let client = Client(spaceId: "<space_id>",
2                    environmentId: "<environment_id>", // Defaults to "master" if omitted
3                    accessToken: "<access_token>")

Accessing data

The Client class manages all requests to the API, and now that you have initialized a Client instance, you can fetch entries. Note that you must retain your Client instance as a property (instance variable) in your application so that asynchronous callbacks are not released by the system before execution.

Fetch one entry:

1client.fetch(Entry.self, id: "nyancat") { (result: Result<Entry>) in
2  switch result {
3  case .success(let nyanCat):
4    print(nyanCat.id) // Prints "nyanCat" to console.
5
6  case .error(let error):
7    print("Oh no something went wrong: \(error)")
8  }
9}

Fetch all entries with content_type = “cat”

1let query = Query.where(contentTypeId: "cat")
2
3client.fetchArray(of: Entry.self, matching: query) { (result: Result<ArrayResponse<Entry>>) in
4  switch result {
5  case .success(let entriesArrayResponse):
6    let cats = entriesArrayResponse.items
7    // Do stuff with cat entries.
8
9  case .error(let error):
10    print("Oh no something went wrong: \(error)")
11  }
12}

A more refined approach

While the above approach is great for quickly fetching data from the API, it can also be useful to retrieve already serialized instances of your own model classes. The EntryDecodable protocol enables said mapping. EntryDecodable actually extends the Decodable protocol which is standard library starting in Swift 4, so all the methods for deserializing your fields should look familiar, and the Contentful Swift client library extends Swift’s native protocols to make things easier.

Let’s get started by implementing a model class, Cat, which will conform to both the EntryDecodable and FieldKeysQueryable protocols:

1final class Cat: EntryDecodable, FieldKeysQueryable {
2
3  static let contentTypeId: String = "cat"
4
5  // FlatResource members.
6  let id: String
7  let localeCode: String?
8  let updatedAt: Date?
9  let createdAt: Date?
10
11  let color: String?
12  let name: String?
13  let lives: Int?
14  let likes: [String]?
15
16  // Relationship fields.
17  var bestFriend: Cat?
18  var image: Asset?
19
20  public required init(from decoder: Decoder) throws {
21    let sys         = try decoder.sys()
22
23    id              = sys.id
24    localeCode      = sys.locale
25    updatedAt       = sys.updatedAt
26    createdAt       = sys.createdAt
27
28    let fields      = try decoder.contentfulFieldsContainer(keyedBy: Cat.FieldKeys.self)
29
30    self.name       = try fields.decodeIfPresent(String.self, forKey: .name)
31    self.color      = try fields.decodeIfPresent(String.self, forKey: .color)
32    self.likes      = try fields.decodeIfPresent(Array<String>.self, forKey: .likes)
33    self.lives      = try fields.decodeIfPresent(Int.self, forKey: .lives)
34
35    try fields.resolveLink(forKey: .bestFriend, decoder: decoder) { [weak self] linkedCat in
36      self?.bestFriend = linkedCat as? Cat
37    }
38    try fields.resolveLink(forKey: .image, decoder: decoder) { [weak self] image in
39      self?.image = image as? Asset
40    }
41}
42
43// If your field names and your properties names differ, you can define the mapping in your `FieldKeys` enum.
44enum FieldKeys: String, CodingKey {
45  case bestFriend, image
46  case name, color, likes, lives
47}

Note: If you want to simplify the implementation of an EntryDecodable, declare conformance to resource, add let sys: Sys to the class definition, and assign that property with sys = try decoder.sys() during initialization. Then, id, localeCode, updatedAt, and createdAt are all provided via the sys property and don’t need to be declared as class members. Note that this style of implementation may make integration with local database frameworks more cumbersome.

Now take a look at what a query on our Cat class would look like. In particular, we’ll create a query where the color field of our cat is set to “gray”.

1let query = QueryOn<Cat>.where(field: .color, .equals("gray"))
2
3// Note the type in the asynchronously returned result: An `ArrayResponse` with `Cat` as the item type.
4client.fetchArray(of: Cat.self, matching: query) { (result: Result<ArrayResponse<Cat>>) in
5  switch result {
6  case .success(let catsResponse):
7    guard let cat = catsResponse.items.first else { return }
8    print(cat.color!) // Prints "gray" to console.
9
10  case .error(let error):
11    print("Oh no something went wrong: \(error)")
12  }
13}

Next steps