Replicas · Authentication Profile

Replicas Authentication

Authentication

Replicas secures its APIs with http and apiKey across 3 declared security schemes, as derived from its OpenAPI definitions.

CompanyAICoding AgentsDeveloper ToolsAutomationCloud WorkspacesMCPDevOps
Methods: http, apiKey Schemes: 3 OAuth flows: API key in: header

Security Schemes

apiKey http
scheme: bearer
engineSecret http
scheme: bearer
workspaceId apiKey
· in: header (X-Workspace-Id)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-20'
method: searched
source: openapi/replicas-openapi-original.json
docs: https://docs.tryreplicas.com/features/api
summary:
  types:
  - http
  - apiKey
  api_key_in:
  - header
  model: >-
    Bearer API-key authentication. Organization admins mint org-scoped API keys
    (Organization -> Settings -> API Keys); any member can mint a personal API
    key scoped to the user. Keys use the prefix `sk_replicas_...` and are sent as
    `Authorization: Bearer <key>`. Agent-mode workspace requests use a separate
    workspace engine secret (bearer) paired with an `X-Workspace-Id` header. One
    automation trigger endpoint (fire custom webhook) is intentionally
    unauthenticated - the URL token is the secret.
schemes:
- name: apiKey
  type: http
  scheme: bearer
  description: >-
    Primary API-key authentication. Obtain your API key from the Replicas
    dashboard under Organization -> Settings -> API Keys. Sent as
    Authorization: Bearer sk_replicas_...
  applied_globally: true
  sources:
  - openapi/replicas-openapi-original.json
- name: engineSecret
  type: http
  scheme: bearer
  description: >-
    Workspace engine secret used by agent-mode workspace requests, paired with
    the X-Workspace-Id header.
  sources:
  - openapi/replicas-openapi-original.json
- name: workspaceId
  type: apiKey
  in: header
  parameter: X-Workspace-Id
  description: Workspace ID used with the engine secret for agent-mode workspace requests.
  sources:
  - openapi/replicas-openapi-original.json