Skip to main content
The Swig IDP SDK is the sign-in layer for Swig apps. Use it when your product needs to authenticate a user first, then continue with a persisted Swig session that another Swig product can use. It lives in swig-idp-sdk and currently ships as @swig-wallet/expo-idp-sdk.

​
What this SDK is for

  • user sign-in with OAuth, email OTP, or SMS OTP
  • browser or Expo-native auth flows
  • isolated-host redirects that return a Swig session
  • handing that session off to wallet or policy flows afterward

​
Continue into the Swig stack

  • Use Developer SDK for hosted wallet preparation and paymaster operations after login.
  • Use the Developer Portal for policy management.
  • Use Protocol SDK for direct protocol instruction building.

​
Choose your path

​
What you get back

Every successful auth flow ends with a persisted Swig session. The session contains:
  • configAddress
  • walletAddress
  • roleId
  • authFlow
That session is the bridge into the next layer of the stack.

Developer SDK

Use the session to continue into hosted wallet creation and transaction flows

Protocol SDK

Use the session if your app will integrate with Swig wallets directly