generated: '2026-07-19'
method: searched
source: https://help.forcepoint.com/fpone/deploy/rhtml/guid-18f77855-8dc9-436a-9fba-179f06a81066.html
docs: https://help.forcepoint.com/fpone/deploy/rhtml/guid-d35197e0-5924-4838-af15-6298cf9e7b50.html
summary:
  types: [oauth2, apiKey, http]
  api_key_in: [header]
  oauth2_flows: [clientCredentials]
  note: >-
    Forcepoint ships several product REST APIs with different auth models; there is no single
    unified gateway. Auth is documented per product in help.forcepoint.com.
schemes:
  - name: sse_oauth2
    product: Forcepoint Data Security Cloud | SSE (Forcepoint ONE)
    type: oauth2
    scheme: bearer
    detail: >-
      OAuth 2.0. Configure API permission levels under Settings > API Interface > OAuth,
      generate a token, then send Authorization: Bearer <token>. Adding a new scope requires
      minting a new token. Config/Log/IP APIs plus SCIM user & group provisioning are gated by scope.
    docs: https://help.forcepoint.com/fpone/deploy/rhtml/guid-18f77855-8dc9-436a-9fba-179f06a81066.html
  - name: ngfw_smc_api_key
    product: Forcepoint NGFW Security Management Center (SMC) API
    type: apiKey
    in: header
    detail: >-
      API key issued by creating an API Client element in the SMC with the required privileges;
      the key authenticates session.login() in the fp-NGFW-SMC-python SDK.
    docs: https://support.forcepoint.com/s/article/How-to-Start-Using-SMC-API
  - name: dlp_basic
    product: Forcepoint DLP REST API
    type: http
    scheme: basic
    detail: >-
      Username/password (management-server admin credentials) exchanged for a session/bearer token
      used on subsequent policy-management calls.
    docs: https://help.forcepoint.com/dlp/90/restapi/index.html
  - name: appliance_basic
    product: Forcepoint Appliance REST API
    type: http
    scheme: basic
    detail: HTTP basic authentication against the appliance host.
    docs: https://help.forcepoint.com/docs/appliance/v85/appliance_api/how_to_use.html