Steno · Authentication Profile

Steno Authentication

Authentication

Steno secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyLegalLegal TechnologyCourt ReportingDepositionsLitigation SupportTranscriptionVideoArtificial IntelligenceSalesforce
Methods: apiKey Schemes: 1 OAuth flows: API key in: unspecified

Security Schemes

StenoApiKey apiKey
· in: unspecified ()

Source

Authentication Profile

steno-authentication.yml Raw ↑
generated: '2026-08-05'
method: searched
source: https://help.steno.com/steno-litify-integration
docs: https://help.steno.com/steno-litify-integration
note: 'Derived mechanically from OpenAPI is not possible — Steno publishes no specification.
  This profile is read from the only public documentation of Steno API credentials:
  the Steno-Litify Salesforce installation guide.'
summary:
  types:
  - apiKey
  api_key_in:
  - unspecified
  oauth2_flows: []
  scopes_published: false
  spec_backed: false
schemes:
- name: StenoApiKey
  type: apiKey
  in: unspecified
  description: 'A confidential, organization-scoped API key. Steno generates one key
    per customer organization on request — the Litify guide instructs the customer
    to send Steno their 18-digit Salesforce Organization ID, and Steno returns the
    key. The key and the Steno API URL are then stored in the Salesforce "Steno Configuration"
    Custom Metadata Type (separate records for Staging and Production), not in a Named
    Credential.'
  issuance: contact Steno (concierge@steno.com or the account manager) with the tenant
    organization ID
  rotation_policy: not published
  sources:
  - https://help.steno.com/steno-litify-integration
  - https://help.steno.com/litify/how-to-retrieve-your-18-digit-org-id
  environments:
  - name: Staging
    note: separate Custom Metadata record
  - name: Production
    note: separate Custom Metadata record
end_user_authentication:
  note: These are the human sign-in controls for Steno's own applications, not API
    credentials. Recorded here because they are the only other published Steno auth
    surface.
  sign_in: https://steno.com/account/sign-in
  controls:
  - name: SAML Single Sign-On
    docs: https://help.steno.com/setting-up-saml-single-sign-on-sso
  - name: Multi-factor authentication
    scope: Firm Dashboard
    docs: https://help.steno.com/how-to-set-up-multi-factor-authentication-mfa-for-your-firm-dashboard
  - name: Role-based access control
    scope: Firm Dashboard
    docs: https://help.steno.com/how-to-enable-role-based-access-control
  - name: Firm Dashboard user roles and access control
    docs: https://help.steno.com/firm-dashboard-access-control
gaps:
- No public API reference documents the header or query parameter the API key travels
  in.
- No OAuth 2.0, OpenID Connect, or scope model is published for the integration API.
- '/.well-known/openid-configuration and /.well-known/oauth-authorization-server are
  404 on steno.com and 403 on api.steno.com.'
x-evidence:
- url: https://help.steno.com/steno-litify-integration
  http_status: 200
  observed: '"The API Key is a confidential and unique key for your organization. If
    you don''t have it yet, please send us your Organization ID, and we will generate
    the key for you." Configured via Setup > Custom Metadata Types > Steno Configuration.'
- url: https://help.steno.com/setting-up-saml-single-sign-on-sso
  http_status: 200
- url: https://api.steno.com/.well-known/openid-configuration
  http_status: 403