Setup

The Para Swift SDK enables you to integrate secure wallet features including creation, passkey-based authentication, and transaction signing into your iOS applications. This guide covers all necessary steps from installation to implementing authentication flows.

Prerequisites

To use Para, you need an API key. This key authenticates your requests to Para services and is essential for integration.

Don’t have an API key yet? Request access to the Developer Portal to create API keys, manage billing, teams, and more.

Installation

Add the Para Swift SDK Package

In your Xcode project, go to File > Add Packages or (in your target) Frameworks, Libraries, and Embedded Content and click +.
Enter https://github.com/getpara/swift-sdk
Select Up to Next Major Version ensuring 2.0.0 < 3.0.0
Add the package to your app target and click Add Package.

Configure Associated Domains for Passkeys

To enable passkeys on iOS, you need to configure Associated Domains:

In Xcode, go to Signing & Capabilities for your app target
Click + Capability and add Associated Domains

Add the following entries:

webcredentials:app.usecapsule.com
webcredentials:app.beta.usecapsule.com

Provide your Team ID + Bundle ID to Para, e.g. A1B2C3D4E5.com.example.yourapp

Without properly registering your domain with Para, passkey authentication flows will fail. Contact Para support if you encounter issues with passkey registration.

Beta Testing Credentials In the BETA Environment, you can use any email ending in @test.getpara.com (like dev@test.getpara.com) or US phone numbers (+1) in the format (area code)-555-xxxx (like (425)-555-1234). Any OTP code will work for verification with these test credentials. These credentials are for beta testing only. You can delete test users anytime in the beta developer console to free up user slots.

Initialization

First, you need to initialize the Para manager in your app. Below is an example of initializing the SDK in a SwiftUI application:

import SwiftUI
import ParaSwift

@main
struct ExampleApp: App {
    @StateObject private var paraManager: ParaManager
    @StateObject private var appRootManager = AppRootManager()

    init() {
        // Simple configuration with API key and environment
        let config = ParaConfig(
            apiKey: "YOUR_API_KEY_HERE",
            environment: .sandbox  // or .beta, .prod
        )
        
        _paraManager = StateObject(wrappedValue: ParaManager(
            environment: config.environment,
            apiKey: config.apiKey,
            appScheme: "paraswift"  // Your app's URL scheme for deep linking
        ))
    }

    var body: some Scene {
        WindowGroup {
            ContentView()
                .environmentObject(paraManager)
                .environmentObject(appRootManager)
        }
    }
}

The appScheme parameter is used for deep linking with external wallets like MetaMask. Make sure to configure your app’s URL scheme in your Info.plist to match this value.

Security Best Practice: Never hardcode your API key in production code. Instead, use environment variables or build configuration:

Add PARA_API_KEY to your scheme’s environment variables or build settings
Access it securely:

let apiKey = ProcessInfo.processInfo.environment["PARA_API_KEY"] ?? ""

Authentication

Para provides a unified authentication experience that supports email, phone, and social login methods. The SDK automatically determines whether a user is new or existing and guides you through the appropriate flow.

Unified Authentication Approach

The recommended approach is to create a single authentication view that handles all authentication methods together. This provides users with all authentication options in one place.

The unified authentication flow automatically detects whether the input is an email or phone number and handles it accordingly.

Handle Email/Phone Submission

Initiate authentication with email or phone:

// Determine if input is email or phone
let auth: Auth
if userInput.contains("@") {
    auth = .email(userInput)
} else {
    auth = .phone(userInput) // Include country code
}

// SDK call: Initiate authentication
let authState = try await paraManager.initiateAuthFlow(auth: auth)

// Handle the result based on stage
switch authState.stage {
case .verify:
    // New user - needs verification
    // Show OTP input UI
case .login:
    // Existing user - complete login
    try await paraManager.handleLogin(
        authState: authState,
        authorizationController: authorizationController,
        webAuthenticationSession: webAuthenticationSession
    )
case .signup:
    // Handle signup after verification
}

Handle OTP Verification

For new users who need verification, handle the OTP flow:

// After user enters the verification code
let verificationCode = "123456" // Get from user input

do {
    // Submit verification code
    let verifiedState = try await paraManager.handleVerificationCode(
        verificationCode: verificationCode
    )
    
    // Complete signup with passkey (preferred) or password
    let method: ParaManager.SignupMethod = paraManager.isSignupMethodAvailable(
        method: .passkey,
        authState: verifiedState
    ) ? .passkey : .password
    
    try await paraManager.handleSignup(
        authState: verifiedState,
        method: method,
        authorizationController: authorizationController,
        webAuthenticationSession: webAuthenticationSession
    )
    
    // User is now signed up and authenticated
} catch {
    // Handle error
}

The unified authentication flow automatically detects whether the input is an email or phone number and handles it accordingly.

Handle Email/Phone Submission

Initiate authentication with email or phone:

// Determine if input is email or phone
let auth: Auth
if userInput.contains("@") {
    auth = .email(userInput)
} else {
    auth = .phone(userInput) // Include country code
}

// SDK call: Initiate authentication
let authState = try await paraManager.initiateAuthFlow(auth: auth)

// Handle the result based on stage
switch authState.stage {
case .verify:
    // New user - needs verification
    // Show OTP input UI
case .login:
    // Existing user - complete login
    try await paraManager.handleLogin(
        authState: authState,
        authorizationController: authorizationController,
        webAuthenticationSession: webAuthenticationSession
    )
case .signup:
    // Handle signup after verification
}

Handle OTP Verification

For new users who need verification, handle the OTP flow:

// After user enters the verification code
let verificationCode = "123456" // Get from user input

do {
    // Submit verification code
    let verifiedState = try await paraManager.handleVerificationCode(
        verificationCode: verificationCode
    )
    
    // Complete signup with passkey (preferred) or password
    let method: ParaManager.SignupMethod = paraManager.isSignupMethodAvailable(
        method: .passkey,
        authState: verifiedState
    ) ? .passkey : .password
    
    try await paraManager.handleSignup(
        authState: verifiedState,
        method: method,
        authorizationController: authorizationController,
        webAuthenticationSession: webAuthenticationSession
    )
    
    // User is now signed up and authenticated
} catch {
    // Handle error
}

Social login is integrated directly into the unified authentication view. Users can authenticate with Google, Apple, or Discord.

Handle Social Login

Implement the social login handler:

private func handleSocialLogin(_ provider: OAuthProvider) {
    Task {
        do {
            let result = await paraManager.handleOAuth(
                provider: provider,
                webAuthenticationSession: webAuthenticationSession,
                authorizationController: authorizationController
            )
            
            if result.success {
                // User successfully authenticated
                appRootManager.setAuthenticated(true)
            } else {
                // Handle error
                print(result.errorMessage ?? "OAuth login failed")
            }
        } catch {
            // Handle error
        }
    }
}

Social Login Buttons

Add buttons for each OAuth provider:

// Google Login
Button("Continue with Google") {
    handleSocialLogin(.google)
}

// Apple Login
Button("Continue with Apple") {
    handleSocialLogin(.apple)
}

// Discord Login
Button("Continue with Discord") {
    handleSocialLogin(.discord)
}

Subsequent Logins

After initial setup, users can log in using their email or phone with the same authentication flow:

// Login with email
let authState = try await paraManager.initiateAuthFlow(auth: .email(userEmail))

// Since the user exists, authState.stage will be .login
if authState.stage == .login {
    try await paraManager.handleLogin(
        authState: authState,
        authorizationController: authorizationController,
        webAuthenticationSession: webAuthenticationSession
    )
    // User is now logged in
}

Alternatively, you can use direct passkey login if you know the user has set up passkeys:

// Direct passkey login (will show all available passkeys if email/phone not provided)
try await paraManager.loginWithPasskey(
    authorizationController: authorizationController,
    email: userEmail, // Optional - helps filter passkeys
    phone: nil
)

This will prompt the user for Face ID or Touch ID verification before granting access to their wallets.

Checking Authentication Status

You can check if a user is already authenticated:

let isLoggedIn = await paraManager.isFullyLoggedIn()

if isLoggedIn {
    // User is authenticated, proceed to main app flow
} else {
    // Show login/signup UI
}

Sign out

To sign out a user and clear their session:

try await paraManager.logout()

Basic Wallet Operations

After successful authentication, you can perform wallet operations:

// Get all user wallets
try await paraManager.fetchWallets() // Ensure we have the latest wallets

if paraManager.wallets.isEmpty {
    // No wallets, perhaps create one
    try await paraManager.createWallet(type: .evm, skipDistributable: false)
    // paraManager.wallets is updated internally
    guard let firstWallet = paraManager.wallets.first else {
        print("Failed to create or find a wallet.")
        return
    }
    
    // Sign a simple message (SDK handles Base64 encoding internally)
    let signature = try await paraManager.signMessage(
        walletId: firstWallet.id,
        message: "Hello, Para!"
    )
    print("Signature: \(signature)")
    
} else {
    // Use existing wallet
    guard let firstWallet = paraManager.wallets.first else { return }
    
    // Sign a simple message (SDK handles Base64 encoding internally)
    let signature = try await paraManager.signMessage(
        walletId: firstWallet.id,
        message: "Hello, Para!"
    )
    print("Signature: \(signature)")
}

For detailed transaction signing with specific blockchains (EVM, Solana, Cosmos), please refer to the respective blockchain integration guides.

Example

For a complete implementation example, check out our Swift SDK example app:

Swift SDK Example App

See an end-to-end example of Para Swift SDK integration.

Next Steps

After integrating Para into your Swift app, you can explore other features and integrations to enhance your Para experience.

EVM Integration

Learn how to use Para as a signer for signing EVM transactions

Solana Integration

Discover how to use Para as a signer for signing Solana transactions

Cosmos Integration

Explore using Para as a signer for Cosmos transactions.

Introduction

Guides

API & Troubleshooting

Setup

Prerequisites

Installation

Initialization

Authentication

Unified Authentication Approach

Subsequent Logins

Checking Authentication Status

Sign out

Basic Wallet Operations

Example

Swift SDK Example App

Next Steps

EVM Integration

Solana Integration

Cosmos Integration

Introduction

Setup

Guides

API & Troubleshooting

​Prerequisites

​Installation

​Initialization

​Authentication

​Unified Authentication Approach

​Subsequent Logins

​Checking Authentication Status

​Sign out

​Basic Wallet Operations

​Example

Swift SDK Example App

​Next Steps

EVM Integration

Solana Integration

Cosmos Integration

Prerequisites

Installation

Initialization

Authentication

Unified Authentication Approach

Subsequent Logins

Checking Authentication Status

Sign out

Basic Wallet Operations

Example

Next Steps