Pimloc · Authentication Profile

Pimloc Authentication

Authentication

Pimloc secures its APIs with http-basic and http-bearer across 2 declared security schemes, as derived from its OpenAPI definitions.

CompanyPrivacyVideo RedactionAnonymizationPIIData ProtectionArtificial IntelligenceComplianceVideo Analytics
Methods: http-basic, http-bearer Schemes: 2 OAuth flows: API key in:

Security Schemes

basicAuth http
scheme: basic
bearerAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-20'
method: searched
source: https://docs.secureredact.co.uk
docs: https://docs.secureredact.co.uk
summary:
  types: [http-basic, http-bearer]
  model: token-exchange
  description: >-
    HTTP Basic authentication with a client_id / client_secret pair (generated
    from the Secure Redact account page) is used only on the token endpoint to
    obtain a short-lived JWT access token. That JWT bearer token authenticates
    all other endpoints. Passing a username to the token endpoint yields a
    user-scoped access token used for the Enterprise Flow.
schemes:
  - name: basicAuth
    type: http
    scheme: basic
    used_on: /api/v3/token
    credentials: client_id (username) + client_secret (password)
    sources: [openapi/secureredact-openapi.yml]
  - name: bearerAuth
    type: http
    scheme: bearer
    bearerFormat: JWT
    used_on: all endpoints except /api/v3/token
    sources: [openapi/secureredact-openapi.yml]
token_endpoint: https://app.secureredact.co.uk/api/v3/token