Skip to main content

Universal User ID

Inside Labs uses a single, canonical identifier for every end user across the platform: the Universal User ID (universalUserId).

Wherever an API takes a user identifier, it expects the universal user ID — not your internal id, not an email, not a phone number.

Why​

The platform aggregates data from many sources — engagement, memberships, bookings, providers — and they all need to agree on who a user is. The universal user ID is that single source of truth, so:

  • the same person looks like the same user to every domain,
  • events about a user can be correlated across domains,
  • you don't have to teach every domain about your internal id format.

Looking one up​

You can resolve a universal user ID from identifiers you already have:

  • by email
  • by email + phone number

Use the lookup endpoint exposed by the user-facing APIs (see the API Reference) to exchange those for a universalUserId, then use that id on subsequent requests.

Best practice​

  • Resolve once, store it. Look up the universal user ID when you first encounter a user, persist it alongside your own user record, and reuse it.
  • Pass universalUserId on every request that's about a specific user.
  • Don't try to derive it from your own ids — always go through a lookup.