Hyland OnBase API
OnBase exposes a multi-surface API stack: a Core REST document API, SOAP AppServer, and legacy COM/.NET assemblies, all tied to Foundation releases. Docs and SDKs sit behind Hyland Community and partner logins, so integration requires partner enablement rather than self-serve signup.
Frequently asked questions
Hyland OnBase scores D on Supergood's API Report Card. OnBase exposes a multi-surface API stack: a Core REST document API, SOAP AppServer, and legacy COM/.NET assemblies, all tied to Foundation releases. Docs and SDKs sit behind Hyland Community and partner logins, so integration requires partner enablement rather than self-serve signup.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Hyland OnBase is the flagship enterprise content services / ECM platform from Hyland Software, headquartered in Westlake, Ohio and founded in 1991.
Primary vertical: misc (horizontal ECM/content services platform sold across regulated and document-intensive industries). A regional hospital system runs OnBase as the system of record for clinical and operational content, scanned consent forms, advance directives, EOBs, prior-auth packets, vendor contracts, and HR files, surfaced inside Epic via the Hyland Epic integration (HL7-driven document context, Epic Hyperspace embedded viewer) and inside Cerner / Oracle Health PowerChart via Hyland's Cerner connector.
High. Hyland reports 14,000+ active customers and 50+ Fortune 100 deployments.
OnBase sits on the content-critical path for the regulated industries that deploy it, by name, it is the system of record for clinical documents inside Epic / Cerner / Oracle Health / MEDITECH workflows, loan files and account documents inside Jack Henry / Fiserv / FIS core banking platforms, claims and policy content inside insurance carriers, case files and public records inside state/local government, and student records / financial aid documents inside Higher Education SIS workflows.
Founded in 1991, headquartered in Westlake, Ohio.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Not that we could find. As of August 2026 there is no official Hyland OnBase MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. Hyland OnBase doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.