Runautomat · Authentication Profile

Runautomat Authentication

Authentication

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

CompanyAutomationRobotic Process AutomationDocument ProcessingArtificial IntelligenceMachine LearningData ExtractioniPaaSAgents
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

BearerAuthScheme http
scheme: bearer · in: header ()

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: searched
source: openapi/runautomat-extract-openapi.json
docs: https://docs.runautomat.com/guides/getting-started/authentication
summary:
  types:
  - http
  http_schemes:
  - bearer
  api_key_prefix: ak_
notes: >-
  All API requests to Automat require an API key passed as an HTTP Bearer token
  in the Authorization header ("Authorization: Bearer ak_..."). API keys are
  scoped to the organization and grant access to all extractors within it. Keys
  are created in the Automat dashboard (Settings -> API Keys), shown once, and
  can be revoked independently. There is no OAuth/OIDC surface on the public
  Extract API.
schemes:
- name: BearerAuthScheme
  type: http
  scheme: bearer
  in: header
  header: Authorization
  format: 'Bearer ak_<api_key>'
  sources:
  - openapi/runautomat-extract-openapi.json