SuprSend · Authentication Profile

Suprsend Authentication

Authentication

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

NotificationsMulti-ChannelEmailSMSPush NotificationsIn-App InboxWhatsAppSlackNotification InfrastructureWorkflow AutomationTemplate Management
Methods: apiKey, http Schemes: 3 OAuth flows: API key in: header

Security Schemes

BearerAuth http
scheme: bearer
ServiceTokenAuth apiKey
· in: header (ServiceToken )
sec0 apiKey
· in: header (Authorization)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/suprsend-rest-api-openapi.yml
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - header
schemes:
- name: BearerAuth
  type: http
  scheme: bearer
  bearerFormat: API_Key
  description: Pass as `Bearer <API_KEY>`. Get API Key from SuprSend dashboard Developers ->
    API Keys section.
  sources:
  - openapi/suprsend-rest-api-openapi.yml
- name: ServiceTokenAuth
  type: apiKey
  in: header
  parameter: ServiceToken <token>
  description: You can get Service Token from [SuprSend dashboard -> Account Settings -> Service
    Tokens](https://app.suprsend.com/en/account-settings/service-tokens) section.
  sources:
  - openapi/suprsend-rest-api-openapi.yml
- name: sec0
  type: apiKey
  in: header
  parameter: Authorization
  description: Bearer authentication header of the form `Bearer <token>`, where <token> is your
    auth token.
  sources:
  - openapi/suprsend-rest-api-openapi.yml