Uniphore U-Capture REST APIs

The U-Capture compliance conversation-recording platform (Red Box heritage) publishes an anonymous, unauthenticated API reference on Uniphore's own documentation portal at support-rb.uniphore.com — fifteen REST API families covering media retrieval and live audio, metadata/annotation/transcription/lock, call suppression, record on demand, export and transcription endpoints, audit, diagnostics, health-monitoring alerts, usage metrics, identity and roles, LDAP mapping, licensing, policy and services configuration. Every API sits behind an API Gateway that handles authentication, throttling, routing and versioning. The reference is feature-and-function level: each API publishes an "API Summary" naming every HTTP request, but paths, verbs, parameters, schemas, status codes and examples are described as being "provided within the APIs" — that is, in the running deployment — so no machine-readable contract is published. U-Capture is customer-deployed and Uniphore publishes no base URL; the entitled API set differs across the Enterprise, Connect and Capture editions.

API entry from apis.yml

apis.yml Raw ↑
name: Uniphore U-Capture REST APIs
description: 'The U-Capture compliance conversation-recording platform (Red Box heritage) publishes an
  anonymous, unauthenticated API reference on Uniphore''s own documentation portal at support-rb.uniphore.com
  — fifteen REST API families covering media retrieval and live audio, metadata/annotation/transcription/lock,
  call suppression, record on demand, export and transcription endpoints, audit, diagnostics, health-monitoring
  alerts, usage metrics, identity and roles, LDAP mapping, licensing, policy and services configuration.
  Every API sits behind an API Gateway that handles authentication, throttling, routing and versioning.
  The reference is feature-and-function level: each API publishes an "API Summary" naming every HTTP request,
  but paths, verbs, parameters, schemas, status codes and examples are described as being "provided within
  the APIs" — that is, in the running deployment — so no machine-readable contract is published. U-Capture
  is customer-deployed and Uniphore publishes no base URL; the entitled API set differs across the Enterprise,
  Connect and Capture editions.'
humanURL: https://support-rb.uniphore.com/conversa/DevelopConversa/DevelopUCaptureV2.0/DevelopUCapture/DevelopUCapture.htm
tags:
- Conversation Recording
- Compliance
- Contact Center
- Speech Analytics
properties:
- type: Documentation
  url: https://support-rb.uniphore.com/conversa/
- type: APIReference
  url: https://support-rb.uniphore.com/conversa/DevelopConversa/DevelopUCaptureV2.0/DevelopUCapture/DevelopUCapture.htm
- type: Webhooks
  url: asyncapi/uniphore-ucapture-webhooks.yml
- type: DataModel
  url: data-model/uniphore-ucapture-data-model.yml
- type: Authentication
  url: authentication/uniphore-authentication.yml
- type: Conventions
  url: conventions/uniphore-conventions.yml
- type: RateLimits
  url: rate-limits/uniphore-rate-limits.yml