# Antiscam SDK (iOS) **Platform:** iOS 17.0+\ **Language:** Swift-first\ **Last Updated:** April 2026 ## Overview Scam Protection SDK for iOS helps organizations add scam, fraud, and phishing protection to their own iOS apps. It combines production-ready UI, public APIs, and platform-integrated protection flows so teams can launch quickly or create tailored in-app experiences. This SDK is designed for organizations embedding protection into an existing iOS application, such as banking, telecom, insurance, and digital service apps. ## What the SDK Provides The SDK supports two common integration styles: * **Built-in experience:** Present ready-made feature screens and reusable UI components * **Custom experience:** Use public APIs, async workflows, and Combine publishers to build your own UI These approaches can also be combined in a single app. ## Core Protection Features ### Safe Call Helps users identify and manage risky incoming calls. * Supports call protection and caller identification experiences * Uses iOS call directory extension patterns for system integration * Supports configurable protection preferences * Exposes extension status and settings-related workflows ### Safe SMS Helps protect users from suspicious SMS content. * Supports SMS filtering and phishing protection experiences * Uses iOS message filtering extension patterns * Supports host-app integration with built-in UI or app-driven workflows ### Safe Email Helps monitor connected mailboxes for phishing and suspicious content. * Supports Gmail, Outlook, and IMAP-based mailboxes * Supports OAuth-based onboarding for supported providers * Supports mailbox validation and multi-mailbox scenarios * Provides mailbox status, scan counts, and threat counts * Supports user preferences for advanced scanning and data settings ### AI Assistant Provides conversational scam detection and security guidance. * Supports natural-language safety and scam questions * Supports file and image scanning flows * Can be used with built-in UI or custom interfaces * Supports real-time interactive experiences and session continuity ### Dashboard Provides a centralized protection summary across enabled features. * Aggregates scan and risk activity across supported protections * Supports built-in UI and custom dashboard development * Supports monthly and per-feature summaries ## SDK Highlights | Capability | Details | | --------------------- | ------------------------------------------------------------------ | | **Language** | Swift-first API with async/await and Combine | | **Integration Model** | Built-in UI, custom UI, or hybrid | | **Lifecycle** | Supports modern iOS app and scene-based architectures | | **Modularity** | Core SDK with optional feature areas | | **Navigation** | Built-in deep linking and flexible routing | | **Branding** | Supports partner app branding and host-driven UX composition | | **iOS Integration** | Designed to work with standard iOS extension and capability models | ## Platform Requirements | Requirement | Version | | ----------------------- | ------------------------------------- | | iOS Deployment Target | 17.0 or later | | Xcode | 26.0 or later | | Swift | 6.2 or later | | Apple Developer Account | Required for signing and capabilities | ### Typical Platform Capabilities Depending on the feature set being integrated, apps may use capabilities such as: * App Groups * Associated Domains * Call-related extension capabilities * Message filter extension capabilities Exact requirements depend on the enabled features and integration approach. ## Architecture at a Glance The SDK is organized so that host-app functionality and extension-related functionality can work within normal iOS platform constraints. ``` Partner Application ├── Main App │ ├── Core SDK │ ├── Safe Call │ ├── Safe SMS │ ├── Safe Email │ ├── AI Assistant │ └── Dashboard │ ├── Call-Related Extensions ├── Message Filter Extension └── Shared App Data ``` The core SDK manages initialization, configuration, status monitoring, feature access, and routing. Feature areas provide their own APIs and UI surfaces. ## What Teams Can Build ### Fast Implementation Use built-in feature screens and standard iOS presentation patterns to add protection quickly with limited custom UI work. ### Fully Custom Experiences Build your own Swift UI or UIKit-based experiences using public APIs for: * call protection settings and state * SMS protection workflows * mailbox monitoring and scan data * assistant sessions and scam analysis results * aggregated dashboard statistics ### Hybrid Experiences Use built-in UI where speed matters and custom UI where product differentiation matters. ## Privacy and User Experience Considerations Some features depend on iOS extensions, capabilities, account connection, or user consent flows. Examples include: * extension enablement for call and SMS protection * mailbox authorization for email protection * host-app messaging to explain protection value and setup steps Apps integrating the SDK should explain the user benefit clearly and align setup flows with platform expectations. ## Feature Availability Feature availability can vary by: * integrated modules * enabled platform capabilities * app configuration * commercial agreement or entitlement model Host apps should be designed to handle cases where some features are available and others are not. ## Who This Is For This SDK is intended for organizations embedding scam protection into their own iOS apps. It is not a consumer standalone app, and it is not intended as a general-purpose public mobile library for unrelated use cases. ## Get Started Scam Protection SDK is available for approved integrations. ### Typical next steps 1. Request access 2. Review the implementation guide 3. Choose the built-in UI, custom UI, or hybrid integration model 4. Integrate the required feature areas 5. Validate extension behavior, capabilities, and branding ### Recommended companion materials * integration guide * API reference * release notes * support and onboarding documentation *Current SDK Version: 3.0.0 · Last Updated: April 2026* --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://even-financial.gitbook.io/developer-center/cyber-safety-and-identity-solutions/antiscam-sdk-ios.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.