App sign-in - Embeddables Docs

Overview

Core always assigns an anonymous app user ID for tracking — no login required. Use this page when end users sign into a portal or another experience where they should have an account, and you want Embeddables to treat them as authenticated app users — not operator or admin login. Today that usually means a customer-facing portal; the API lives on Core so other SDKs can reuse the same phone OTP flow. Anonymous identity keeps working alongside sign-in. While someone is logged in, use their authenticated id for work that should follow the account; useAppUserId() still returns the device id. Phone OTP runs through embeddables.auth on the same Core instance you already initialized — see Overview & setup first.

JavaScript
React

await embeddables.auth.requestOtp({ phone: '+15551234567' })

const session = await embeddables.auth.verifyOtp({
  phone: '+15551234567',
  token: '123456',
})
session.app_user_id

embeddables.auth.getEffectiveUserId()

await embeddables.auth.logout()

Show signed-in UI with hooks:

import { useIsAuthenticated, useAuthenticatedUserId } from '@embeddables/core/react'

function Account() {
  const isAuthenticated = useIsAuthenticated()
  const authenticatedUserId = useAuthenticatedUserId()

  if (!isAuthenticated) return <SignInForm />
  return <p>Signed in as {authenticatedUserId}</p>
}

Call requestOtp, verifyOtp, and logout on the instance from useEmbeddables().

Sandbox publishable keys accept passcode 0000.

Optional auth settings on initEmbeddables (sandboxUser, apiUrl) are documented in the Reference. Live vs sandbox follows your publishable key.

Reference

Method and hook details — auth, useIsAuthenticated(), and useAuthenticatedUserId() — are in the Core reference.

​Overview

​Sign-in flow

​Reference

Overview

Sign-in flow

Reference