Pimloc Secure Redact API

The Secure Redact API API from Pimloc — 0 operation(s) for secure redact api.

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/pimloc-secure-redact-api-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

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

Get an API key

Free tier, no email required.

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

OpenAPI Specification

pimloc-secure-redact-api-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Secure Redact API
  version: v3
  x-generated: '2026-07-20'
  x-method: searched
  x-source: https://docs.secureredact.co.uk (public Postman collection "Secure Redact API - v3")
  description: 'Secure Redact is Pimloc''s AI-powered platform for automated redaction of personally identifiable information (PII) from video, audio, images and documents — blurring faces, license plates, screens, text and full bodies. The v3 REST API lets you upload media by URL or file, monitor processing via status callbacks (webhooks) or polling, trigger redaction, and download the redacted media and audio transcripts. Two flows are supported: a Standard Flow (fully automated, no UI) and an Enterprise Flow (review/edit in the Secure Redact UI, with projects and users). Authentication is a token exchange: HTTP Basic (client_id / client_secret) on the token endpoint returns a short-lived JWT bearer token used on all other endpoints.'
  contact:
    name: Secure Redact Support
    url: https://www.secureredact.ai/contact-us
  termsOfService: https://www.secureredact.ai/terms-of-service
servers:
- url: https://app.secureredact.co.uk
  description: Secure Redact v3 production API
tags:
- name: Secure Redact API
paths: {}
webhooks:
  stateCallback:
    post:
      operationId: stateCallbackEvent
      summary: Media state callback
      description: If a state_callback URL was supplied on upload, Secure Redact periodically POSTs media progress/status messages to it as the media moves through the workflow (e.g. detected, completed).
      requestBody:
        content:
          application/json:
            schema:
              type: object
              description: Media state/progress event payload.
      responses:
        '200':
          description: Acknowledged
      tags:
      - Secure Redact API
  exportCallback:
    post:
      operationId: exportCallbackEvent
      summary: Export callback
      description: If an export_callback URL was supplied on upload, Secure Redact POSTs the exported media info to it once redaction completes. Requests are authenticated with the supplied export_token.
      requestBody:
        content:
          application/json:
            schema:
              type: object
              description: Export/completed event payload.
      responses:
        '200':
          description: Acknowledged
      tags:
      - Secure Redact API
components:
  securitySchemes:
    basicAuth:
      type: http
      scheme: basic
      description: HTTP Basic using client_id (username) and client_secret (password), only on /api/v3/token.
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Short-lived JWT access token returned by /api/v3/token.