Every request must be authorized. The API sits behind Silmo’s WorkOS-backed organization auth: your credentials resolve to an organization, and everything a session produces — audio, transcript, the filled document — is stored and served strictly within that organization’s namespace.

​
Bearer token

Send your token on every request:
Tokens are provisioned per organization during onboarding. If you don’t have credentials yet, contact your Silmo representative — [email protected].

​
Data isolation

  • Sessions are scoped to the organization that created them. A session id from another tenant returns 404, never data.
  • Stored artefacts (recordings, session state, filled documents) live under an organization-scoped prefix in encrypted object storage.
  • Sessions and their artefacts are retrievable after completion, so a review can happen hours later or by a teammate with a shared link.

​
Environments