Connect a client via API or SFTP

Use an API or SFTP integration when a client has an established document workflow you do not want to disrupt — for example, invoices stored in a file server, a cloud drive, or a custom internal portal.

Which option to use?

Both routes deliver documents into the same data-capture pipeline as any other channel. Choose based on what the client’s system can support.

Where: Requires setup with the ECIT Digital team and the client’s IT contact.

1. Decide which integration type fits the client:

   Type	How it works	Typical use case
   REST API	Your system calls Nordflow’s document upload endpoint to push PDFs programmatically.	Client uploads to a cloud drive (e.g. OneDrive); a custom job pushes PDFs from there into Nordflow. Digitising historic invoices from a file server.
   SFTP	Nordflow hosts an SFTP endpoint. The client drops PDFs into a folder and Nordflow ingests them on a schedule.	Clients or suppliers with established SFTP-based document transfer workflows.

2. Contact the ECIT Digital team to provision the integration endpoint for the client.

3. Share the connection details with the client’s IT contact so they can configure their system to push documents to Nordflow.

Related: Connect an e-invoice network