Bring therapeutic play into your platform.

The browser half of Level 1 — the whole PlaySpace workspace in your page — in full:

'use client'
import { ShellEmbed } from '@playspace-health/embed/react'

export function PlaySpaceWorkspace() {
  return (
    <div style={{ height: 820 }}>
      <ShellEmbed
        baseUrl="https://agentic-ps.playspace.health"
        fetchToken={async () => {
          const res = await fetch('/api/playspace/workspace-token', { method: 'POST' })
          return ((await res.json()) as { token: string }).token
        }}
      />
    </div>
  )
}

The credential that can do everything stays on your server. fetchToken calls your own route, which exchanges it for a token scoped to one clinician, the capabilities that screen needs, and the origins you named — and re-mints into the running frame before it expires, so a long session never outlives its token.

Not a JavaScript stack? Nothing here requires one. The server half is a plain HTTPS call and the browser half is an iframe, so a page rendered by Python, PHP, Java, C# or Ruby mounts the same workspace. Using the API from other languages is that whole path.

How it fits together

1. 1

   You create the records

   Clinics, practitioners, patients and appointments, through the Partner API, with an idempotency key on every write. PlaySpace assigns the identifiers and you keep them alongside your own.

2. 2

   You mint a credential for the moment

   Session links for an appointment, or a short-lived embed token scoped to one clinician. Both are minted on your server from a credential that never reaches a browser.

3. 3

   You render, or you do not

   Drop a component from @playspace-health/embed into your own page and hand it a token callback, or send the two links and let PlaySpace host the whole session.