OpenText

Supergood | OpenText API

Alex Klarfeld

Alex Klarfeld

— 7 min read
Supergood | OpenText API

Programmatically access matter workspaces, documents, versions, metadata, and legal holds from OpenText with a stable REST API. Supergood builds and operates production-grade, unofficial OpenText integrations so your team can automate ECM/DMS workflows—and interoperate with iManage—without heavy custom engineering.

Plain English: 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 workspaces, folders, and documents with versions and metadata—and push new documents, update attributes, apply legal holds, and publish records.

For a tech company integrating with OpenText (especially if your customer’s day-to-day documents live in iManage), this means you can mirror client/matter hierarchies, ingest finalized documents from iManage for records retention, keep metadata in sync, and expose OpenText search and preview inside your app. You can build features like automated closing binder assembly, defensible legal-hold orchestration, cross-repository matter dashboards, and background jobs that publish executed agreements from iManage to OpenText with consistent governance.

What is OpenText?

OpenText (https://www.opentext.com) 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)

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
  • 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

Available Endpoints

Authentication

POST /sessions: Establish a session using credentials. Supergood manages MFA (SMS, email, TOTP) and SSO/OAuth when enabled. Returns a short-lived auth token maintained by the platform.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/sessions \
  --header 'Authorization: Basic <Base64 encoded token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "username": "[email protected]",
    "password": "<password>",
    "mfa": { "type": "totp", "code": "123456" }
  }'

Example response

{
  "authToken": "eyJhbGciOi...",
  "expiresIn": 3600,
  "user": {
    "id": "u_otx_72b19f",
    "name": "Records Administrator",
    "entitlements": ["matters", "documents", "versions", "legal_holds"]
  }
}

POST /sessions/refresh: Refresh an existing token to keep sessions uninterrupted.

Matters

GET /matters: List matter workspaces with filters for client, matter number, status, and update windows.

Query parameters

  • clientId: string
  • matterNumber: string
  • status: open | closed | archived
  • updatedFrom, updatedTo: ISO 8601 timestamps
  • page, pageSize: integers for pagination

Example response

{
  "items": [
    {
      "matterId": "mat_5f2d1c",
      "clientId": "CL-10021",
      "matterNumber": "M-45877",
      "title": "Acquisition of Apex Labs",
      "status": "open",
      "workspaceId": "ws_9b4c2e",
      "path": "/Clients/CL-10021/Matters/M-45877",
      "owners": [{"userId": "u_otx_72b19f", "name": "Records Administrator"}],
      "metadata": {
        "practiceGroup": "Corporate",
        "responsiblePartner": "Jane Patel",
        "openDate": "2025-11-03"
      },
      "createdAt": "2025-11-03T10:22:11Z",
      "updatedAt": "2026-01-18T14:02:09Z"
    }
  ],
  "page": 1,
  "pageSize": 50,
  "total": 1
}

POST /matters: Create a new matter workspace using a template and initial attributes.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/matters \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "clientId": "CL-10021",
    "matterNumber": "M-45901",
    "title": "Series B Financing",
    "templateKey": "Matter-Corporate",
    "metadata": {
      "practiceGroup": "Corporate",
      "responsiblePartner": "Alex Chen",
      "openDate": "2026-02-15"
    },
    "security": {
      "groups": ["Corporate-Team", "Records-Admins"],
      "ethicalWall": true
    }
  }'

Example response

{
  "matterId": "mat_61c0af",
  "workspaceId": "ws_1cfeb2",
  "path": "/Clients/CL-10021/Matters/M-45901",
  "status": "open",
  "createdAt": "2026-02-15T09:04:33Z"
}

Documents

POST /documents: Upload a document into a matter workspace (supports chunked uploads) and set metadata/security.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/documents \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "matterId": "mat_61c0af",
    "folderPath": "/Clients/CL-10021/Matters/M-45901/Final/Agreements",
    "fileName": "Stock_Purchase_Agreement_v5.pdf",
    "contentType": "application/pdf",
    "upload": {"type": "base64", "data": "JVBERi0xLjQK..."},
    "metadata": {
      "documentType": "Agreement",
      "counterparty": "Apex Labs",
      "executed": true
    },
    "security": {
      "inherit": true,
      "additionalGroups": ["Deal-Team-Apex"]
    },
    "checkinComment": "Executed SPA filed for records"
  }'

Example response

{
  "documentId": "doc_94a3d7",
  "version": {
    "versionId": "ver_2f88d1",
    "number": "5.0",
    "status": "checked_in"
  },
  "path": "/Clients/CL-10021/Matters/M-45901/Final/Agreements/Stock_Purchase_Agreement_v5.pdf",
  "createdAt": "2026-02-15T09:05:12Z"
}

GET /documents: List documents by matter with version and metadata summaries.

Query parameters

  • matterId: string (required for matter scoping)
  • folderId or folderPath: string
  • updatedFrom, updatedTo: ISO 8601 timestamps
  • page, pageSize: integers for pagination

Example response

{
  "items": [
    {
      "documentId": "doc_94a3d7",
      "name": "Stock_Purchase_Agreement_v5.pdf",
      "version": "5.0",
      "author": {"userId": "u_otx_72b19f", "name": "Records Administrator"},
      "contentType": "application/pdf",
      "size": 1048576,
      "metadata": {"documentType": "Agreement", "executed": true},
      "security": {"inherit": true, "groups": ["Corporate-Team", "Records-Admins", "Deal-Team-Apex"]},
      "createdAt": "2026-02-15T09:05:12Z",
      "updatedAt": "2026-02-15T09:05:12Z"
    }
  ],
  "page": 1,
  "pageSize": 50,
  "total": 1
}

PATCH /documents/{documentId}/metadata: Update category attributes and access controls.

curl --request PATCH \
  --url https://api.supergood.ai/integrations/<integration_id>/documents/doc_94a3d7/metadata \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "metadata": {"executed": true, "closingDate": "2026-02-14"},
    "security": {"additionalGroups": ["Finance-Reporting"]}
  }'

Example response

{
  "documentId": "doc_94a3d7",
  "metadata": {"documentType": "Agreement", "executed": true, "closingDate": "2026-02-14"},
  "updatedAt": "2026-02-15T11:22:01Z"
}

POST /legal-holds: Create or apply a legal hold to a matter and custodians (users/groups).

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/legal-holds \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "name": "Apex_Litigation_Hold_2026",
    "reason": "Pending litigation against Apex Labs",
    "scope": {"matterId": "mat_61c0af"},
    "custodians": {
      "users": ["[email protected]", "[email protected]"],
      "groups": ["Corporate-Team"]
    },
    "notifications": {"send": true, "message": "You are placed on legal hold for Apex Labs matter."}
  }'

Example response

{
  "holdId": "hold_a71c02",
  "status": "active",
  "appliedScopes": [{"matterId": "mat_61c0af"}],
  "custodians": {"users": 2, "groups": 1},
  "createdAt": "2026-02-15T12:10:43Z"
}

GET /legal-holds: List holds with filters for status, scope, and update windows.

Query parameters

  • status: active | released
  • matterId: string
  • updatedFrom, updatedTo: ISO 8601 timestamps
  • PSA: page, pageSize

[Get full API sop Specs →](https:// NB Laurate)

[Get full sop API Specs →](https://book.vimcal.com/p/alexklar inline collapse)

[Get full API Specs →](https://book hazardcall010 ) Harvard set ya

[Get full API Specs →](https://book.vimcal.com/p pipeline/alexklarfeld/30-minute-meeting sop )

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)

Performance Characteristics

  • 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

Getting Started

  1. Schedule Integration Assessment

Book a 30-minute session to confirm your modules, licensing, and authentication model.

  1. Supergood Builds and Validates Your API

We deliver a hardened OpenText adapter tailored to your workflows and entitlements.

  1. Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as OpenText evolves.

Schedule Integration Call →

Frequently Asked Questions

Q: Which OpenText modules can this integration cover?

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.

Q: How are MFA and SSO handled for automation?

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.

Q: Do you support large-file and resumable uploads?

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.

Q: Can you map iManage client/matter structures and metadata to OpenText?

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.

Q: Do you support on-prem and cloud deployments?

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.

iManage API - Programmatically access iManage Work with Supergood

Ready to automate your OpenText workflows?

Supergood can have your OpenText integration live in days with no ongoing engineering maintenance.

Get Started →

Read more