> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getpara.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Email & Phone Login
> Implement Para's unified email and phone authentication flow in Swift.
export const DemoCallout = ({variant = "card", title = "Interactive Demo", description = "Try the live demo to explore authentication flows and customize your modal before integrating."}) => {
if (variant === "subtle") {
return
;
};
export const Link = ({href, label, newTab = false}) => {
const [isHovered, setIsHovered] = useState(false);
return setIsHovered(true)} onMouseLeave={() => setIsHovered(false)}>
{label}
;
};
## Overview
Para One Click Login is the default experience—Para hosts the entire flow for existing users and new signups. If you turn on passkey or password requirements in the Developer Portal, the optional sections below show how to handle them.
**Beta Testing Credentials** In the `BETA` Environment, you can use any email ending in `@test.getpara.com` (like
[dev@test.getpara.com](mailto: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.
## 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 to create API keys, manage billing, teams, and more.
Need to install the SDK? Start with the .
Para ships with One Click enabled. You can add requirements like Passkey-only signup or password fallback from the . Adjust the optional sections below only if you turn on those features.
## Start the Authentication Flow
Inject the Para manager and authentication helpers, then launch the flow with whichever identifier your UI collects (email or phone). Para One Click handles the rest unless you enable extra verification.
```swift AuthenticationView.swift theme={null}
import AuthenticationServices
import ParaSwift
struct AuthenticationView: View {
@EnvironmentObject var paraManager: ParaManager
@Environment(\.authorizationController) private var authorizationController
@Environment(\.webAuthenticationSession) private var webAuthenticationSession
@State private var pendingState: AuthState? // Only used if you enable OTP/passkey requirements
var body: some View {
VStack {
// Render your auth UI and call startAuth(identifier:)
}
.task {
paraManager.setDefaultWebAuthenticationSession(webAuthenticationSession)
}
}
private func startAuth(identifier: String) {
let auth: Auth = identifier.contains("@")
? .email(identifier.lowercased())
: .phone(identifier) // Expect E.164 format
Task {
do {
let state = try await paraManager.initiateAuthFlow(auth: auth)
switch state.stage {
case .done:
completeLogin()
case .verify:
// Store state to finish OTP/passkey signup later if you enabled it
pendingState = state
case .login:
try await paraManager.handleLogin(
authState: state,
authorizationController: authorizationController
)
completeLogin()
case .signup:
// Signup completes after OTP + passkey if required
break
}
} catch {
// Handle errors according to your UI needs
}
}
}
}
```
The `completeLogin()` helper can mark your app as authenticated and transition to the signed-in experience:
```swift AuthenticationView.swift theme={null}
private func completeLogin() {
// Mark the user as authenticated in your app
}
```
## Handle OTP Signup (Optional)
Only implement this step if you turn on OTP / passkey signup in the Developer Portal. Collect the OTP, exchange it for a verified state, and finish signup:
```swift AuthenticationView.swift theme={null}
private func submitOtp(_ code: String) {
guard let pendingState else { return }
Task {
do {
let verifiedState = try await paraManager.handleVerificationCode(
verificationCode: code
)
try await paraManager.handleSignup(
authState: verifiedState,
method: .passkey,
authorizationController: authorizationController
)
completeLogin()
} catch {
// Handle errors according to your UI needs
}
}
}
```
If you skip `setDefaultWebAuthenticationSession(_:)`, `initiateAuthFlow` returns a `loginUrl` you can present manually using `presentAuthUrl(_:context:webAuthenticationSession:)`. The automatic `.done` stage shown above relies on the default session being set.
## Support Direct Passkey Login
If you already know a user has passkeys registered, you can offer a shortcut that skips email/phone input:
```swift AuthenticationView.swift theme={null}
private func loginWithPasskey(email: String?) {
Task {
do {
try await paraManager.loginWithPasskey(
authorizationController: authorizationController,
email: email,
phone: nil
)
completeLogin()
} catch {
// Handle errors according to your UI needs
}
}
}
```
## Next Steps
* Add social providers alongside this flow in
* Manage existing sessions with