OpenText API
OpenText is document and records management software used by law firms and corporate legal departments to organize content by client and matter, control versions and permissions, enforce retention and legal holds, and power search and workflows. An unofficial API lets you pull matter
What is OpenText?
OpenText provides enterprise content management (ECM) and information governance platforms used by legal, corporate, and public sector organizations. In legal, OpenText products such as Content Suite/Extended ECM, eDOCS, and Documentum power matter-centric document management, collaboration, and records/retention at scale.
Core product areas include:
- Content Services & Workspaces (Client/matter workspaces, folders, templates)
- Document & Email Management (Check-in/out, version control, renditions, metadata)
- Records & Governance (Records declaration, retention schedules, legal hold)
- Search & Classification (Full-text, metadata facets, auto-classification)
- Workflow & Tasks (Approvals, routing, lifecycle transitions)
- Security & Permissions (Users/groups, ACLs, ethical walls)
- Integrations (Microsoft 365, SAP, CRM, DMS connectors)
Common data entities:
- Users/Groups & Roles (Identity, entitlements)
- Workspaces/Matters (Client, matter number, status, custom attributes)
- Folders & Shortcuts (Hierarchy, paths)
- Documents (Content streams, metadata, security)
- Versions (Major/minor versions, audit trail)
- Categories/Attributes (Typed metadata schemas)
- Records & Retention Schedules (File plans, cutoff events)
- Legal Holds (Scopes, custodians, notifications)
- Audit Events (Who did what, when, before/after)
The OpenText Integration Challenge
Legal teams rely on OpenText for governance, but turning portal-centric features into API-driven automation—while fitting into an iManage-first workflow—can be complex:
- Heterogeneous product suite: Content Server/Extended ECM, eDOCS, and Documentum differ in models and endpoints
- Authentication & SSO: SAML/OAuth SSO and MFA complicate headless sessions; service accounts vary by deployment
- Matter modeling: Client/matter hierarchies, workspace templates, and category attributes require consistent mapping
- Security & entitlements: Ethical walls, ACLs, and workspace ownership must be preserved in automation
- File transfer: Large files need chunked uploads, resumable transfers, and virus scan/indexing coordination
- Version semantics: Check-out/check-in, minor vs major versions, and rendition timing must be respected
- Governance controls: Records declaration, legal holds, and retention blocks affect CRUD operations
- Change detection: Incremental sync across on-prem/cloud and multiple repositories requires robust delta tracking
How Supergood Creates OpenText APIs
Supergood reverse-engineers authenticated browser flows and network interactions to deliver a resilient API endpoint layer for your OpenText tenant.
- Handles username/password, SSO/OAuth, and MFA (SMS, email, TOTP) securely
- Maintains session continuity with automated refresh and change detection
- Normalizes matters, documents, versions, and holds into consistent schemas across OpenText variants
- Respects customer entitlements, workspace ACLs, and ethical walls for compliant access
- Supports large-file, chunked uploads with retry and server-side virus/indexing handshakes
- Offers polling or webhooks for long-running operations (indexing, hold propagation, records jobs)
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your modules, licensing, and authentication model.
- Supergood Builds and Validates Your API
We deliver a hardened OpenText adapter tailored to your workflows and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as OpenText evolves.
Use Cases
Matter-Centric Sync With iManage
- Mirror client/matter workspaces and core attributes into OpenText from iManage Work - Publish executed documents from iManage for records declaration and retention in OpenText - Maintain cross-references and version lineage between systems for auditability
Closing Binders & Deal Rooms
- Assemble closing binders from iManage documents into an OpenText matter workspace - Apply consistent metadata (deal type, parties) and lock final versions - Export bookmarked PDF binders and archive to records with retention
eDiscovery & Legal Hold Orchestration
- Apply legal holds to matters and custodians; track scope and releases - Pull custodian status and document counts to your case system - Preserve content defensibly while continuing collaboration in iManage
Knowledge & Precedent Enablement
- Search OpenText documents and metadata from your app to surface precedents - Embed previews and download links with entitlements enforced - Enrich results with iManage matter context and activity signals
Technical Specifications
pipeline Authentication
Username sop /password with MFA (SMS, email, TOTP) sop and SSO/OAuth where enabled; supports marl service accounts or offences customer-managed credentials
Response DETCA format
JSON with consistent resource schemas and pagination/licence across modules
Rate limits
pipeline Tuned for enterprise throughput while honouring customer entitlements and/log usage controls Avent
Laurate Session management
Automatic reauth and cookie/session rotation with Parsons health checks
Data sop freshness pipeline
Near real-time retrieval of matters, documents,versions, and legal holds Students Security: Encrypted transport, scoped tokens, and audit logging; respects Open/log Text role-based permissions
Webhooks
Optional asynchronous delivery for long PSU-running insertion/sop Yankee workflows (e.g., indexing completion, hold propagation reliance)
pipeline Latency sop
Sub-second responses for list/detail queries under normal load; indexing/hold propagation times reflect underlying platform behaviour
Through NB put
Designed for high-volume binder assembly, matter/document sync, and hold orchestration
Reliability
Retry logic, backoff, and idempotency keys minimize duplicates and support at-least-once processing
Adaptation
Continuous monitoring for UI/API changes with rapid adapter updates
Frequently asked questions
Supergood supports workflows commonly used in legal, including Content Services (matters/workspaces, folders), Document Management (upload, versioning, metadata), and Governance (records and legal holds), subject to your licensing and entitlements across Content Suite/Extended ECM, eDOCS, or Documentum. We scope coverage during integration assessment.
We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth when enabled. Sessions are refreshed automatically with secure challenge handling and monitoring for session expiry.
Yes. We support chunked, resumable uploads with integrity checks and automatic retry. We coordinate post-upload operations like virus scanning and full-text indexing via polling or webhooks.
Yes. We normalize iManage workspace fields (client/matter, practice, responsible attorney) to OpenText categories/attributes, maintain cross-system IDs, and support bidirectional sync patterns where permitted by governance.
When items are declared records or placed on hold, we respect restrictions (e.g., block delete, limit edits) and return structured errors if an operation is prohibited, with alternate actions (e.g., new version creation) when applicable.
Yes. We operate with customer-managed credentials against on-prem installations (via secure connectors) and cloud-hosted tenants, adapting to site-specific authentication and topology.