Skip to main content
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.

​
At a glance

Prerequisites
  • An organization with at least one tenant, project, and registered app.
  • OAuth credentials from your wearable vendor (WHOOP, Garmin, Fitbit, and others in the vendor catalog) when configuring a cloud integration.
  • An API key with ingestion allowlisting if your app sends on-device HSI snapshots; this path is separate from vendor OAuth.
Keep the organization and tenant selectors correct before debugging empty lists. Most project-scoped pages require both to be set.

​
Step 1: Sign in and set workspace context

Goal: Authenticate, scope the dashboard to the right organization and tenant, and open the project you want to work in.

​
1.1 Sign in

  1. Open platform.synheart.ai.
  2. Complete sign-in when prompted. Supported methods:
    • Email and Password
    • Continue with Google
    • Continue with GitHub
  3. 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.

​
1.2 Select organization and tenant

In the left sidebar, use the two switchers above the navigation links:
  1. Organization switcher: dropdown header Organizations. Pick the company account that owns your projects.
  2. 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.”

​
1.3 Open a project

  1. From Projects (/projects), click a project card.
  2. Confirm the Overview page loads at /projects/{projectId}.
What you see: The sidebar switches to Project navigation with the following items:

​
Step 2: Connect a wearable integration

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.

​
2.1 Choose where to manage wearables

You can manage wearables from two equivalent surfaces: Both surfaces open the same Add Wearable / Edit Wearable drawer.

​
2.2 Review hub KPIs

On Wearables, four summary cards appear at the top:

​
2.3 Start the setup wizard

  1. On Wearables, click Setup new wearable.
    • The button is disabled until the project has at least one app; register an app under Apps first.
  2. In the Add Wearable drawer, complete the form:
  1. 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.

​
Integration status labels

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.

​
2.4 Finish vendor-side setup

  1. Copy any Webhook URLs from the success panel into the vendor developer portal.
  2. Open the Provider Portal link and complete redirect URI registration, webhook endpoints, and user authorization as required.
  3. 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.

​
Filter the wearables list

​
Step 3: View imported session data

Goal: Confirm data is ingesting and locate individual snapshots in the project Sessions explorer.

​
3.1 Open the session explorer

  1. In the project sidebar, click Sessions (/projects/{projectId}/sessions).
  2. Confirm the page title Sessions and subtitle {project name} · Session explorer.
Default date range: 30D (last 30 days). KPI comparison labels adapt to the preset (e.g. vs yesterday, vs last week, vs last month).

​
3.2 Read KPI cards

Each card shows a period-over-period delta based on the selected date range.
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.

​
3.4 Session list columns

​
Step 4: Inspect a single session

Goal: Open one snapshot, review structured fields and charts, and export the raw JSON if needed.

​
4.1 Open session detail

  1. In the sessions table, click a Snapshot ID.
  2. The detail page opens at /projects/{projectId}/sessions/{sessionRef}?source=….
What you see:
  • Page title Session detail
  • Subtitle: Snapshot payload, axes, and related metrics for this session.
  • Export JSON button (top right)
  • Snapshot detail section: a view-descriptor-driven layout rendered from the payload

​
4.2 Export the payload

  1. Click Export JSON.
  2. A file named session-{sessionId}.json downloads.
What is included: The full session record in its native JSON format. Internal infrastructure fields are omitted from the download.

​
4.3 Understand the Snapshot detail view

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:
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.

​
Biosignal fields (when present in payload)

​
Reference: project overview KPIs

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.

​
Troubleshooting

See also Troubleshooting and Projects.

​
Next steps

Projects

Create projects, add apps, and understand the resource hierarchy.

API keys

Issue keys and request ingestion allowlisting for on-device data.

Synheart Wear

Learn how device adapters capture biosignals on mobile and watch.

Synheart Session

See how sessions are produced before they appear in the platform.