Step-by-step guide to sign in, connect a wearable OAuth integration, and inspect imported session data in the Synheart Platform
This guide walks through the primary workflow on platform.synheart.ai: sign in, set your organization and tenant context, connect a third-party wearable to a registered app, and explore the session data that flows in.Each step covers what to do in the UI, what you should see, and what the results mean. Use this page after you have completed Create a platform account and registered at least one app inside a project.
The platform is invite-only today. If you do not have access yet, request an invite before starting.
Complete sign-in when prompted. Supported methods:
Email and Password
Continue with Google
Continue with GitHub
If multi-factor authentication (MFA) is enabled on your account, enter your 6-digit TOTP code on the Two-factor authentication screen (or use a recovery code).
What you see: After a successful login, you land on Projects (/projects) unless you arrived via an invitation or deep link.
In the left sidebar, use the two switchers above the navigation links:
Organization switcher: dropdown header Organizations. Pick the company account that owns your projects.
Tenant switcher: dropdown header Tenants. Pick the workspace (tenant) that contains the project.
What you see: Project lists, wearables, and sessions load for the selected pair. If no tenant exists yet, you may see No tenant yet with a Create your first tenant action on Projects.What you do if blocked: Create a tenant at Tenants (/tenants) or ask an organization administrator to invite you to one.
Wearables and sessions wait for a valid organization + tenant pair. Without a tenant, lists stay empty and you may see messages such as “Create a tenant for this organization to load wearables.” or “Select a workspace (tenant) to load project API keys.”
Goal: Register an OAuth integration between a platform app and a vendor API so biosignals can flow in once the integration is Active.Wearable connections are OAuth integrations: one row per vendor × app. The platform stores encrypted credentials and scopes; your mobile app or vendor webhooks deliver data after setup completes.
The button is disabled until the project has at least one app; register an app under Apps first.
In the Add Wearable drawer, complete the form:
Form field
Description
App
Registered app that owns this vendor connection
Device Type
Vendor from the active catalog
Client ID
OAuth client ID from the vendor developer portal
Client Secret
OAuth client secret (never shown again after save)
App Redirect URI
OAuth callback URL registered with the vendor
Scopes
Permission keys for this vendor; required scopes are pre-selected
Submit the form.
What you see on success: The drawer shows Integration created with optional Webhook URLs, a Provider Portal link, and Setup Notes with vendor-specific instructions.
Each app supports one integration per vendor type. If Device Type has no options, every catalog vendor may already be connected for that app; use Edit Wearable on an existing row instead.
Copy any Webhook URLs from the success panel into the vendor developer portal.
Open the Provider Portal link and complete redirect URI registration, webhook endpoints, and user authorization as required.
Return to the platform and confirm the row shows Active.
Data import timing:
Webhook-driven vendors: biosignals arrive when the vendor POSTs to Synheart webhook URLs.
On-device SDK path: sessions appear after your app ingests HSI snapshots with an allowlisted API key, independent of OAuth status in the wearables list.
Restrict to sessions from a linked wearable device type
Export
Downloads a CSV containing Snapshot ID, Observed, Producer · App, Source, and Windows
If the table is empty, widen the range to 30D or Custom, confirm ingestion allowlisting for HSI data, and verify the correct organization and tenant are selected.
The Snapshot detail section uses a backend view descriptor to render tables, stat cards, and charts dynamically. Depending on HSI schema version and payload shape, you may see:
Section type
Typical content
Stat / key-value panels
Session metadata, app context, timing
Axis tables or cards
HSI axes by domain (cognitive, affective, …)
Line / bar / radar charts
Time-series or aggregate metrics
Enum-labeled fields
Dominant emotion, activity state
Older snapshots may show fewer sections if axes or biosignals were not captured. Use Export JSON to inspect the full payload when a field appears missing in the UI.
The Overview page (/projects/{projectId}) shows complementary aggregates for the selected 1D / 7D / 30D / Custom range. Use it for trends; use Sessions for row-level inspection.
KPI
Description
Total Subjects
Distinct users with snapshots in the selected range
