How does the technical data exchange work?
API or SFTP, full loads by default, and a sync cadence you choose: how the pipeline gets seeded and kept current.
First, the terms. SFTP is a secure protocol for transferring files between systems in scheduled batches. An API is a direct connection where one system requests records from another in real time.
Both work for getting data into TechWolf: a direct API, or file-based transfer over SFTP or an S3 bucket, hosted by TechWolf or by you. File-based transfer is the most common path, because many enterprise source systems lack a strong native API.
We default to full data loads rather than deltas. Full loads are less error-prone and scale better; deltas remain an option where API rate limits or volumes demand them. Sync cadence is your design decision, not ours: daily, weekly, or monthly, with daily as the finest granularity we support.
A typical rollout starts with one large initial load to seed the system, followed by recurring syncs on the cadence you configure. Plan for some lead time on whitelisting, credentials, and infrastructure before the pipeline goes live. Which systems we connect to is covered in a separate answer.