GitHub repository: putio-sdk-swift The Swift Package product and module are PutioSDK The CocoaPods package is PutioSDK The existing public SDK type names remain PutioAPI

Install with Swift Package Manager in Xcode using:

https://github.com/putdotio/putio-sdk-swift.git

Or add it to Package.swift:

dependencies: [
    .package(url: "https://github.com/putdotio/putio-sdk-swift.git", from: "1.0.0")
]

Then depend on the PutioSDK product.

Import it as:

import PutioSDK

If you use CocoaPods today, install with:

pod 'PutioSDK'

import PutioSDK

let api = PutioAPI(
    config: PutioAPIConfig(
        clientID: "<your-client-id>",
        token: "<your-access-token>"
    )
)

api.getAccountInfo { result in
    switch result {
    case .success(let account):
        print(account.username)
    case .failure(let error):
        print(error.message)
    }
}

The repo exposes one local verification command:

make verify

Use make bootstrap first on a fresh clone. make verify installs the example workspace, prefers any Xcode-advertised iPhone simulator destination on iOS 26.0+, and falls back to the installed iphonesimulator SDK when Xcode is not exposing one yet

Releases are continuous on main: every merge is treated as releasable. Conventional commits drive version selection through semantic-release, GitHub releases run automatically after make verify passes, and CocoaPods publishing runs from the same workflow when COCOAPODS_TRUNK_TOKEN is configured

The example app shows a minimal ASWebAuthenticationSession flow and a follow-up account fetch:

• Example/PutioAPI/ViewController.swift
• Example/README.md

• CONTRIBUTING.md for local setup and verification
• SECURITY.md for private vulnerability reporting
• AGENTS.md for repo-specific agent guidance
• Example for the example app and smoke-test workspace

Start with CONTRIBUTING.md so local setup, verification, and release expectations stay aligned with CI

This project is available under the MIT License