Home / API
Redaction API
Add redaction to your own product without building a detection stack. Upload, trigger analysis, start a job, receive status, retrieve the output.
Two Shapes
Fully automated
For high-volume routine work where nothing needs a human.
- Upload media by API
- Trigger AI analysis
- Start the redaction job
- Receive status through webhooks
- Retrieve the redacted file
Everything runs in the background. Your system never opens the file.
Hybrid, with review in the loop
For sensitive or high-risk content where a person has to sign off.
- Upload by API
- AI detects faces, objects and PII
- Analysts review and correct in Studio Space
- Final redaction is applied
- Your system retrieves the approved output
This is the shape most public-sector integrations take, because the release is consequential and the review step is what makes it defensible.
Technical
| Architecture | REST, versioned endpoints |
| Specification | OpenAPI |
| Authentication | OAuth client credentials, plus service application credentials for machine access |
| Notifications | Webhooks, against a documented event catalog, with delivery logs |
| Operations | Upload and manage media, trigger detection, start redaction, download output, access metadata, logs and custody history |
| Deployment | Cloud, hybrid, private cloud and on-premises — the API is the same in all of them |
Beyond the API
For deeper embedding the platform also offers JavaScript widgets, UI extension apps, player plugins, a server object model, delegated permission passthrough and a partner app model. If you need Studio Space to appear inside your own application rather than alongside it, that is the route.
Where It Matters
- S3-to-S3 pipelines — bucket in, bucket out, no duplicate storage
- Microsoft 365 — Teams recordings, SharePoint, Exchange archives
- Digital evidence platforms, public-records portals, eDiscovery tools, VMS platforms, claims systems
What The Redaction API Does Not Do
- Automated redaction applies what the detector found at the configured threshold. For a consequential release, the hybrid shape exists for a reason.
- Bulk processing is queued work; throughput follows available AI processing capacity.
- Bulk redaction is permissioned per format, and API credentials carry the same per-format rights as a user.
How The Redaction API Is Evaluated
- REST API with a published OpenAPI specification.
- OAuth client-credentials authentication, with separate service application credentials.
- Webhooks against a documented event catalog, with delivery logs.
- Both zero-touch and human-in-the-loop flows are supported by the same API.
- Available identically on cloud, private cloud and on-premises deployments.
- Deeper embedding available through widgets, UI extension apps and a partner app model.
Get the Spec
Tell us the workflow and we will send the OpenAPI spec and a sandbox.