Sendspark · Authentication Profile

Sendspark Authentication

Authentication

Sendspark secures its APIs with apiKey and oauth2 across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode, refresh_token, and device_code flow(s).

CompanyVideoSalesMarketingPersonalizationArtificial IntelligenceVideo MessagingWebhooksMCP
Methods: apiKey, oauth2 Schemes: 3 OAuth flows: authorizationCode, refresh_token, device_code API key in: header

Security Schemes

apiKey apiKey
· in: header (x-api-key)
apiSecret apiKey
· in: header (x-api-secret)
mcpOAuth oauth2

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: searched
source: openapi/sendspark-openapi-original.json
docs: https://help.sendspark.com/api-reference
summary:
  types:
  - apiKey
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - authorizationCode
  - refresh_token
  - device_code
schemes:
- name: apiKey
  type: apiKey
  in: header
  parameter: x-api-key
  sources:
  - openapi/sendspark-openapi-original.json
- name: apiSecret
  type: apiKey
  in: header
  parameter: x-api-secret
  sources:
  - openapi/sendspark-openapi-original.json
- name: mcpOAuth
  type: oauth2
  note: >-
    The hosted MCP server (apiv2.sendspark.com/api/mcp) authenticates over OAuth 2.0
    via browser sign-in (issuer https://auth.sendspark.com), separate from the REST
    API's x-api-key/x-api-secret header auth.
  issuer: https://auth.sendspark.com
  metadata: https://apiv2.sendspark.com/.well-known/oauth-authorization-server
  scopes_supported: [openid, profile, email, offline_access]
  sources:
  - well-known/sendspark-oauth-authorization-server.json
notes: >-
  REST API calls require BOTH x-api-key and x-api-secret headers; keys are
  workspace-scoped. GET /v1/workspaces/identifier resolves the workspace id for a
  key pair.