Reference · built on requestConnectorFiles, documents & spreadsheets

DocuWare

File cabinets, documents, index fields, and workflow tasks in DocuWare Cloud and on-premises through the Platform REST API.

Request accessPricing ↗

About

DocuWare is a document management and workflow system sold as DocuWare Cloud or installed on premises. Its Platform REST API, under the /DocuWare/Platform path of your system, represents organizations, file cabinets, document trays, dialogs, documents, sections, and pages as linked resources in XML or JSON. Each document carries index fields. Workflow tasks and instances are exposed under RequestsWorkflows.

Through Fibric, an operator lists the documents in a file cabinet, reads their index fields, and proposes an index change or an upload of a new document. You approve it. A receipt records what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from DocuWare and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Organizations and file cabinets through /DocuWare/Platform/Organizations and /DocuWare/Platform/FileCabinets
  • Documents in a file cabinet or document tray through FileCabinets/{id}/Documents, paged through the result's next link
  • A document's index fields, and its sections and pages, by following the links the document resource carries
  • Search and result-list dialogs through FileCabinets/{id}/Dialogs?dialogType=Search, and the DocumentsQueryResult a DialogExpression returns
  • Workflow tasks and workflow instances through RequestsWorkflows/Tasks and RequestsWorkflows/Workflows
  • The document file itself through FileDownload, as the original with targetFileType=Auto or as PDF with annotations

Proposed actions

  • Target capability: propose an upload through POST FileCabinets/{id}/Documents as multipart/form-data, with index fields in the document part
  • Target capability: propose an index change through PUT FileCabinets/{id}/Documents/{docId}/Fields, listing each FieldName and Item before it applies

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Match an invoice before it is paid

    The operator lists new documents in the invoice file cabinet, reads the supplier, amount, and PO index fields, and proposes a match against the purchase order and receipt in your ERP.

    With Three-Way Match

  • Stop the same invoice twice

    The operator searches the cabinet by supplier and invoice number, flags a second document with the same values, and proposes an index change marking it a duplicate.

    With Duplicate Invoice

  • Renew before the contract lapses

    The operator reads the expiry field on each contract document and proposes a reminder to the owner ahead of the date.

    With Contract Lapse

Requirements

  • DocuWare 7.8 or later for OAuth, and 7.11 or later for login with an App Registration and the Authorization Code flow
  • An App Registration with its Application (Client) ID, scope, and redirect URL, which DocuWare makes mandatory from April 2026
  • A DocuWare user account for the integration, since logon takes a UserName and a LicenseType
  • For on-premises systems, network reach from Fibric to the /DocuWare/Platform endpoint
Authentication
OAuth 2.0 through the DocuWare Identity Service with an App Registration created on the Configuration page; access tokens last 60 minutes, and cookie logon remains for DocuWare 7.10 and older.

Limits

  • Access tokens expire 60 minutes after issue; a service must request a new one before then to avoid interruption
  • DocuWare Cloud answers a document query with at most 10,000 elements; larger counts return a 422, so lists run in pages of about 1,000
  • Only Username & Password, DocuWare Token, Trusted User, and Windows Authentication grant types are supported, the last two on premises only
  • No event feed is documented; the connector polls documents and workflow tasks rather than receiving pushes

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request DocuWare ↗

Questions and answers

Which DocuWare versions does the Platform REST API support with OAuth?
OAuth arrived in DocuWare 7.8 with DocuWare.Platform.ServerClient 13. Versions 7.8 to 7.10 accept OAuth with the same features as cookie authorization, and App Registration becomes mandatory from April 2026. Version 7.11 and later add login with an App Registration through the Authorization Code flow, with SSO from Microsoft Entra ID.
How does Fibric change an index field?
With a PUT to FileCabinets/{id}/Documents/{docId}/Fields. The body is a Field array where each entry names the FieldName, the new Item, and its ItemElementName, such as String. The request needs Accept and Content-Type set to application/json.
Does DocuWare send events when a document is stored?
Not through the Platform REST API pages Fibric read. Workflow Manager's Web Service Activity lets a workflow call a SOAP web service and read results back, but that is a call out from a workflow, not a document event feed. Fibric lists documents and tasks on a schedule.
Ask about DocuWare

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with DocuWare through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy