ATOM · Authentication Profile

Atom Authentication

Authentication

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

CompanyMessagingWhatsAppArtificial IntelligenceConversational CommerceChatbotsSalesLead GenerationCustomer EngagementLatin America
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

apiKey apiKey
· in: header ()

Source

Authentication Profile

atom-authentication.yml Raw ↑ 
generated: '2026-07-18'
method: searched
source: https://soporte.atomchat.io/knowledge/api-de-clientes
docs: https://soporte.atomchat.io/knowledge/api-de-clientes
notes: >-
  No OpenAPI is published for the Atom (atomchat.io) API, so this profile is
  captured from the provider's knowledge base rather than derived from a spec.
  The Atom Customers API and WhatsApp template-message API are called over HTTPS
  and authenticated with an account API key generated in the Atom admin panel and
  supplied on each HTTP request (documented via the knowledge-base articles on
  configuring the key in Postman / HTTP requests). Header name and exact placement
  are not published in the public docs and are intentionally left unspecified here
  rather than guessed.
summary:
  types:
  - apiKey
  api_key_in:
  - header
  oauth2_flows: []
schemes:
- name: apiKey
  type: apiKey
  in: header
  description: >-
    Account API key issued from the Atom admin panel, sent on each request to the
    Atom Customers and WhatsApp template-message APIs.
  sources:
  - https://soporte.atomchat.io/knowledge/api-de-clientes