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.
Dependency Installation
Install the required packages for Para SDK integration:Project Setup
Platform-Specific Configuration
In order for passkeys to work, you need to set up associated domains in your Xcode project linked to the Para domain.

Set Up Associated Domains
- Open your project in Xcode
- Select your target and go to “Signing & Capabilities”
- Click ”+ Capability” and add “Associated Domains”
- Add the following domains:
- webcredentials:app.beta.usecapsule.com
- webcredentials:app.usecapsule.com
Important: Your
teamId + bundleIdentifier
must be registered with the Para team to set up associated domains. For example, if your Team ID is A1B2C3D4E5
and Bundle Identifier is com.yourdomain.yourapp
, provide A1B2C3D4E5.com.yourdomain.yourapp
to Para. This is required by Apple for passkey security. Note: Allow up to 24 hours for domain propagation.Install CocoaPods for native dependencies:
Remember to run
pod install
after adding new dependencies to your project.Configure Metro Bundler
Create or updatemetro.config.js
in your project root:
metro.config.js
Add Para Shim
Import the Para shim as the FIRST import in your application’s entry file (typicallyindex.js
):
Important: The shim import must come before any other imports to ensure required modules are available.
Using the Para SDK
The Para SDK provides two main authentication methods: email-based and phone-based. Each method supports creating a new user and logging in an existing user. Both flows utilize Native Passkeys for secure and seamless authentication. Follow the steps below to implement these flows in your React Native application.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.Create New User with Email
This flow guides you through the process of registering a new user with email, verifying their email, and setting up their wallet.Initialize Para Client
First, set up the Para client to enable SDK interactions:If you’re using a legacy API key (one without an environment prefix) you must provide the
Environment
as the first argument to the ParaMobile
constructor. You can retrieve your updated API key from the Para Developer Portal at https://developer.getpara.com/Sign Up or Log In
Use thesignUpOrLogIn
method to handle both new user registration and existing user authentication:Verify Email
Once the user receives the verification code, call theverifyNewAccount
method to confirm their email:Register Passkey
Use the returned authState to register the user’s passkey:Complete New User Flow
Implement the full flow by combining all the previous steps:Login Existing User with Email
This flow demonstrates how to authenticate an existing user using their email and passkey.Login Existing User
For existing users, use thesignUpOrLogIn
method which will return a login stage, then use loginWithPasskey
:Wallet Management
After successful authentication, you must create wallets for the blockchain networks you want to use:Creating Wallets
Retrieving Wallet Information
Complete Integration Example
Important: Wallet creation must be completed after authentication but before any blockchain operations (signing transactions, getting balances, etc.).
Examples
For practical implementation of the Para SDK in React Native environments, check out our GitHub repository:React Native Integration Examples
Troubleshooting
If you encounter issues during the integration or usage of the Para SDK in your React Native application, here are some common problems and their solutions:Para SDK initialization fails
Para SDK initialization fails
If you’re having trouble initializing the Para SDK:
- Ensure that you’ve called
para.init()
after creating the Para instance. - Verify that you’re using the correct API key and environment.
- Check that all necessary dependencies are installed and linked properly.
- Look for any JavaScript errors in your Metro bundler console.
Native modules are not found or linked
Native modules are not found or linked
If you’re seeing errors about missing native modules: - Run
pod install
in the ios
directory to ensure all
CocoaPods dependencies are installed. - For Android, make sure your android/app/build.gradle
file includes the
necessary dependencies. - Rebuild your app after adding new native dependencies. - If using Expo, ensure you’ve run
expo prebuild
to generate native code.Passkey operations fail or throw errors
Passkey operations fail or throw errors
If passkey creation, retrieval, or usage isn’t working: - Verify that you’ve set up associated domains correctly for
both iOS and Android. - For iOS, check that your
entitlements
file includes the necessary associated domains. - For
Android, ensure your asset_statements
are correctly configured in your AndroidManifest.xml
. - Make sure you’ve
provided the correct SHA-256 fingerprint to the Para team for Android. - Check for any permission-related errors in
your logs.Crypto-related errors or undefined functions
Crypto-related errors or undefined functions
"Cannot create URL for blob" errors
"Cannot create URL for blob" errors
If you’re encountering blob URL creation errors during passkey operations:
- Ensure you’re using
{ disableWorkers: true }
in the ParaMobile constructor - Verify the Para SDK shim is imported first in your
index.js
file - This error occurs when Web Workers are enabled in React Native environments
Authentication fails or API requests are rejected
Authentication fails or API requests are rejected
If you’re experiencing authentication issues:
- Double-check that your API key is correct and properly set in your environment variables.
- Verify you’re using the correct environment (
BETA
orPRODUCTION
) that matches your API key. - Ensure your account has the necessary permissions for the operations you’re attempting.
- Check your network requests for any failed API calls and examine the error messages.