generated: '2026-10-19'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://tinycommand.com/docs/forms/fields/connection
sources:
- https://tinycommand.com/docs/forms/fields/connection
- https://tinycommand.com/docs/mcp/authentication
- https://tinycommand.com/docs/account/api-keys
- https://tinycommand.com/docs/forms/getting-started
description: Authentication methods for TinyCommand
schemes:
- type: http-bearer
  name: Workspace API Key
  evidence: Every request to the Tiny Command MCP server is authenticated with a workspace API key sent as a bearer token.
  location: header
  header: Authorization
  how_to_obtain: Generate, list, and revoke keys in the platform under MCP keys. Issuing keys requires a workspace Admin or Owner role.
- type: oauth2
  name: Connection field OAuth
  evidence: When a respondent reaches this field, they see a button to connect their account via OAuth -- they click it, sign in to the service,
    grant permissions, and return to the form with a valid authorization token stored in the submission.
docs: https://tinycommand.com/docs/forms/fields/connection