Uptycs · Authentication Profile

Uptycs Authentication

Authentication

Uptycs publishes no public API reference (per-customer docs live in-product on each https://{stack}.uptycs.io tenant), but the authentication model is documented publicly through the official Uptycs pack for Cortex XSOAR. Each API user downloads a credentials file from the Uptycs console containing an API key, API secret, the stack domain, and the customer ID. Clients mint a short-lived HS256 JWT (iss = API key, exp = now + 3600s, signed with the API secret) and send it as an Authorization Bearer token, along with an RFC 1123 date header, to https://{stack}.uptycs.io/public/api/customers/{customerId}.

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

SecurityCybersecurityCNAPPXDRCloud SecurityEndpoint SecurityKubernetes SecurityosqueryThreat DetectionCompliance

Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

UptycsApiJwt http

scheme: bearer

Source

Authentication Profile

generated: '2026-07-21'
method: searched
source: https://github.com/demisto/content/blob/master/Packs/Uptycs/Integrations/Uptycs/Uptycs.py
docs: https://xsoar.pan.dev/docs/reference/integrations/uptycs
description: >-
  Uptycs publishes no public API reference (per-customer docs live in-product
  on each https://{stack}.uptycs.io tenant), but the authentication model is
  documented publicly through the official Uptycs pack for Cortex XSOAR. Each
  API user downloads a credentials file from the Uptycs console containing an
  API key, API secret, the stack domain, and the customer ID. Clients mint a
  short-lived HS256 JWT (iss = API key, exp = now + 3600s, signed with the API
  secret) and send it as an Authorization Bearer token, along with an RFC 1123
  date header, to https://{stack}.uptycs.io/public/api/customers/{customerId}.
summary:
  types:
    - http
  schemes:
    - bearer
  bearer_format: JWT (HS256)
  api_key_in: []
  oauth2_flows: []
schemes:
  - name: UptycsApiJwt
    type: http
    scheme: bearer
    bearerFormat: JWT
    description: >-
      Self-signed HS256 JWT minted by the client from a per-user API key
      (claim iss) and API secret (signing key), expiring within one hour.
      Credentials are issued per user, per customer stack, from the Uptycs
      console (user profile > API keys). No OAuth 2.0 / OIDC surface is
      published.
    sources:
      - https://github.com/demisto/content/blob/master/Packs/Uptycs/Integrations/Uptycs/Uptycs.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/uptycs-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.

GitHub Google LinkedIn

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