Push Security · Authentication Profile

Push Security Authentication

Authentication

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

CompanyEnterpriseSecurityIdentityBrowser SecuritySaaS SecurityCybersecurityThreat DetectionSIEM
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

pushApiToken apiKey
· in: header ()

Source

Authentication Profile

push-security-authentication.yml Raw ↑ 
generated: '2026-07-20'
method: searched
source: https://pushsecurity.com/help/audience/engineering/rest-v1
docs: https://pushsecurity.com/help/audience/engineering/rest-v1
summary:
  types: [apiKey]
  api_key_in: [header]
  notes: >-
    Push exposes a REST API (v1) to programmatically administer the platform,
    served from https://api.pushsecurity.com. Access is authenticated with an
    API token generated by an administrator in the Push admin console; the
    unauthenticated API host returns HTTP 403 "Missing Authentication Token".
    Exact header name and scope catalog are documented in the authenticated
    admin console and the REST v1 reference (JavaScript-rendered) and were not
    captured verbatim in this pass — recorded conservatively without fabrication.
schemes:
- name: pushApiToken
  type: apiKey
  in: header
  description: >-
    Administrator-issued API token presented on each request to the Push REST
    API. Tokens are created and scoped in the Push admin console.
  sources: [docs]