> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL. > > Documentation indexes by section: > - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt > - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt > - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt > - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt > > Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth > Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks > > OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json > MCP server: https://docusign.docs.buildwithfern.com/_mcp/server # iOS SDK 101 overview > Our iOS SDK provides methods and classes that enable mobile developers to access the functionality of the Docusign eSignature REST API. ## iOS SDK 101 overview The Docusign iOS SDK is designed to streamline app development for the iOS platform. This SDK provides methods and classes that enable mobile developers to access the functionality of the [eSignature REST API](/docs/esign-rest-api). This SDK also includes unique capabilities specific to mobile app scenarios, such as signing documents in an online or offline mode or syncing signed documents from your own mobile app. ## Places to start If you’re new to Docusign development, familiarize yourself with core Docusign API development concepts: * [Platform 101](/platform): Discover the power of Docusign APIs and learn about the overall development process. * [Authenticate](/platform/auth): All API calls to Docusign services must be authenticated. The Docusign iOS SDK supports Authorization Code Grant and JSON Web Token Grant authentication flows. Read about how to find the best authentication flow for your project. * [eSignature concepts](/docs/esign-rest-api/esign101/concepts): Learn how to attach signable documents to envelopes, use templates, set tabs for signing, specify and authenticate recipients, and more. * [Core mobile SDK interfaces](/docs/mobile-sdks/ios-sdk/ios101/core-interfaces): Understand how to perform the core tasks needed for mobile integrations. * [Docusign Connect](/platform/webhooks/connect): Rather than poll the API for status on your envelopes, configure a webhook listener for Docusign Connect, the Docusign webhook service. * [Go-Live](/platform/go-live): When you’re ready to deploy your mobile app to use the Docusign production environment, follow this process to migrate your app from your developer account to production. ## Create a developer account Before you begin, you will first need to create a free Docusign developer account. You’ll also need to configure an app and an associated integration key to make SDK calls. An *integration key* uniquely identifies your app and is also used as your client ID during OAuth token requests. See [Build a Docusign integration](/platform/build-integration) for more information about the overall process. ## Install the iOS SDK The [Docusign iOS SDK](https://github.com/docusign/native-ios-sdk) is available from our open-source GitHub repository. See the [iOS SDK README.md](https://github.com/docusign/native-ios-sdk#readme) file for instructions on installation and setup. ## Compatibility Developers using the Docusign iOS SDK must use the following versions or later of relevant software: * Objective-C 2.0 or Swift 4.2 * iOS 10 * XCode 12.0 ## iOS SDK versioning New versions of the iOS SDK are released periodically to use the latest features of the eSignature REST API or to add new features that are specific to mobile scenarios. SDK versions use the standard period-separated [semantic versioning](https://semver.org/) scheme. General release versions are in the form of x.y.z, and release candidate (prerelease) versions are of the form x.y.z-rc. The Docusign [iOS SDK changelog](https://github.com/docusign/native-ios-sdk/blob/master/CHANGELOG.md) lists notable changes in the current and prior versions of the iOS SDK. Developers are not required to update their applications to new versions of the SDK unless there’s a specific reason to do so, such as: * To access a new SDK feature or method. * To adopt an SDK bug fix including security-related issues. * To support an updated version of one of the SDK's dependencies. ## Sample app Our sample app is a great way to get started with mobile development for Docusign integrations. You can run the sample app to get an idea of what the iOS SDK can do for you by outlining scenarios for a fictitious company without needing to install or configure anything. To clone and run a sample app, create a developer account (if you don’t already have one), open the sample app page, and clone the apps you want from their open source GitHub code under the MIT license. To find out more information and to try it, see the [iOS SDK sample app](/docs/mobile-sdks/ios-sdk/sample-app) page. > Our iOS SDK provides methods and classes that enable mobile developers to access the functionality of the Docusign eSignature REST API. ## Docs - [What’s included in the iOS SDK](https://developers.docusign.com/docs/mobile-sdks/ios-sdk/ios101/whats-included.md): See what's included in our iOS SDK for eSignature REST API. - [When to use the iOS SDK](https://developers.docusign.com/docs/mobile-sdks/ios-sdk/ios101/when-to-use.md): Our iOS SDK wraps the Docusign eSignature REST API functionality into a package that is optimized for mobile development. - [iOS SDK core interfaces](https://developers.docusign.com/docs/mobile-sdks/ios-sdk/ios101/core-interfaces.md): The iOS SDK core interfaces are methods that you call to perform basic tasks. - [iOS SDK status and error codes](https://developers.docusign.com/docs/mobile-sdks/ios-sdk/ios101/status-and-error-codes.md): When using the iOS SDK, your application should handle errors thrown by the eSignature REST API or errors that the SDK itself generates.