Appaegis · Authentication Profile

Appaegis Authentication

Authentication

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

CompanySecurityZero TrustEnterprise BrowserAccess ManagementData Loss PreventionGenAI SecurityIdentitySASE
Methods: apiKey, http Schemes: 3 OAuth flows: API key in: header

Security Schemes

apiKeySecret apiKey
· in: header ()
idTokenHeader apiKey
· in: header ()
bearerAuth http
scheme: bearer

Source

Authentication Profile

appaegis-authentication.yml Raw ↑
generated: '2026-07-17'
method: searched
source: https://github.com/appaegis/api-script-samples/blob/main/lib/common.py
docs: https://github.com/appaegis/api-script-samples#prerequisite
summary:
  types: [apiKey, http]
  api_key_in: [header]
  http_schemes: [bearer]
  model: token-exchange
  note: >-
    No published OpenAPI/OIDC discovery document is available; this profile is
    derived from the provider's public api-script-samples repository (lib/common.py)
    and README, which document the real authentication flow verbatim.
flow:
  description: >-
    Two-step token-exchange. An API key (apiKey) and secret (apiSecret) are issued
    in the Mammoth Cyber management portal under "Setting -> Admins & API Keys ->
    API Keys" (the secret is displayed once and can be downloaded as a dotenv file).
    The client POSTs the apiKey/apiSecret pair to the authentication endpoint and
    receives a short-lived idToken, which is then presented on subsequent calls.
  token_exchange:
    method: POST
    url: https://api.mammothcyber.net/api/v2/authentication
    request_content_type: application/json
    request_body: '{ "apiKey": "...", "apiSecret": "..." }'
    response_field: Authorization
    returns: idToken (JWT)
  presenting_the_token:
    - surface: REST (v1 + v2)
      header: idToken
      value: <idToken>
    - surface: GraphQL (/graphql, /api/graphql)
      header: Authorization
      value: Bearer <idToken>
schemes:
  - name: apiKeySecret
    type: apiKey
    in: header
    description: >-
      apiKey + apiSecret credential pair exchanged at /api/v2/authentication for an
      idToken. Created and revoked in the management portal.
    sources: [https://github.com/appaegis/api-script-samples/blob/main/lib/common.py]
  - name: idTokenHeader
    type: apiKey
    in: header
    parameter_name: idToken
    description: Short-lived idToken presented on REST v1/v2 requests.
    sources: [https://github.com/appaegis/api-script-samples/blob/main/lib/common.py]
  - name: bearerAuth
    type: http
    scheme: bearer
    bearer_format: JWT
    description: Same idToken presented as a Bearer token on the GraphQL endpoint.
    sources: [https://github.com/appaegis/api-script-samples/blob/main/block-list-pac-v2.py]

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/appaegis-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.