Every request knows which user it belongs to.
Backapp gives each device in your app an identity the moment it first connects — no sign-up screen, no auth server of your own. Subscription status and AI usage are tied to that identity from the first request.
{
"user_id": "user_8f2a…",
"type": "anonymous",
"platform": "ios",
"token": "bk_user_…"
}No sign-up wall
Users reach your first screen without creating an account. Identity is created silently on the device.
No auth server to run
Token issuing, storage and validation live in Backapp. Your app holds a token; your backend holds nothing.
One identity, every workflow
Subscription status and AI usage are attached to the same user record — nothing to stitch together later.
Three calls, and the user exists.
- 1App launches and registers the device.Your app sends the device identifier with your project key. Backapp creates an anonymous user.
- 2Backapp returns a user token.Store it securely on the device. It identifies the user on every later request.
- 3Every workflow call carries the token.Subscription checks and AI requests resolve the user from it — no extra parameters.
// CONTENT PENDING: replace with the verified example
import * as SecureStore from 'expo-secure-store';
const deviceId = await getOrCreateDeviceId();
const res = await fetch(`${BACKAPP_API_URL}/identity/devices`, {
method: 'POST',
headers: { 'X-Project-Key': BACKAPP_PROJECT_KEY },
body: JSON.stringify({ device_id: deviceId, platform: 'ios' }),
});
const { user, token } = await res.json();
await SecureStore.setItemAsync('backapp_token', token);
// every later call: Authorization: Bearer <token>{
"user": {
"id": "user_8f2a…",
"type": "anonymous",
"created_at": "2026-11-16T09:12:04Z",
"subscription": { "status": "none" }
},
"token": "bk_user_…"
}What a user is in Backapp.
A user is a record Backapp owns. Your app reads it through the token; subscription and AI workflows write to it.
id- Stable identifier Backapp assigns on first launch.
type- "anonymous" today; sign-in types appear as they are confirmed.
platform- iOS or Android, from the registration call.
subscription- Status reported by your subscription integration (Adapty).
created_at- When the identity was first created.
Anonymous, device-based
One identity per install, created on first launch. Enough for subscriptions, usage limits and AI access without asking the user for anything.
Additional sign-in flows
Sign-in methods that link an anonymous identity to an account appear here as each one is verified.
The user is the key the rest of Backapp turns on.
Usage limits and subscription status aren’t separate systems to connect — they read from the same identity.
Questions about identity?
Do users have to create an account?
No. Identity is created on the device at first launch. Users reach your first screen without a sign-up step.
What happens if the user reinstalls the app?
A reinstall creates a new anonymous identity unless a sign-in flow links it to an account. Store restores for subscriptions are handled by your billing integration.
Where is the token stored?
On the device, in your platform’s secure storage. Backapp never asks your app to persist credentials anywhere else.
Can I link an anonymous user to an email or Apple ID later?
Additional sign-in flows are listed in the docs as they are confirmed. Until then identity is anonymous and device-based.
Does identity work with Adapty?
Yes. The access level Adapty grants is stored against the same Backapp user, so supported workflows can check it on each request.
Ship without building auth.
Identity, subscriptions and AI workflows from one backend.