The DocuMotor platform can be onboarded with or without the services of Omnidocs. This article outlines the requirements for anyone onboarding DocuMotor.


The most important component for leveraging the DocuMotor platform is data. There are no specific requirements for the data format, but one of the most common formats used with DocuMotor is JSON.

Send data (POST)

In order to transform your data and receive a document from DocuMotor, you need to be in a position to forward your data to the DocuMotor API. Meaning that you need to have some sort of plugin or development capability in whatever system where you keep your data to be able to formulate a payload and forward it to the DocuMotor endpoint.

Transformation of data

As soon as data has been sent to DocuMotor, you have the possibility to transform it. This means structuring the data into a form that makes it easy to bind it into fields and other types of content within the document. DocuMotor has a vast selection of transformation capabilities. Read more about it here: Reference, Guides, and Tutorials.


You need a template where the result of the transformed data is passed to. The template can be a Word document, PowerPoint presentation, Excel spreadsheet, or it can be a YAML pipeline.


At last, you need to be able to store the response from DocuMotor. This can either be on the system you’re integrating with or in the users’ download folder.