Files as Integration Glue

Somewhere in your estate a CSV is running the company. Decades into the age of APIs, an enormous share of the world's application integration still travels as files. These include the nightly extract, the price list, the claims batch, and the ledger feed. This is not backwardness. Files decouple systems in time, survive either side rebooting, batch beautifully, and audit naturally. They work with software whose only integration option is import and export. The file interface is a pattern worth doing well, not apologizing for. The CSV was never the problem; the interface contract that was an email is.

This series treats the file interface as the engineering discipline it is. It covers the honest case for files against APIs, the interface contract both sides sign, and flat-file formats that age well. It covers acknowledgment patterns that prove receipt (and get read), and error handling across a boundary owned by two teams. It also covers evolving an interface without breaking the other side. None of it is glamorous, and all of it is why the nightly feed keeps running after everyone who built it has moved on.

Articles in This Series

• Why Files Are Still the Universal Integration Interface
  This article makes the honest case: time decoupling, batch economics, auditability, and universal support. It covers the cases where an API genuinely serves better, so you can defend the choice either way.
• Designing a File Interface Contract
  This article covers the specification both sides sign: format, naming, schedule, delivery method, acknowledgment, and error behavior. It includes a worked contract document you can copy and adapt.
• Choosing Flat-File Formats That Age Well
  This article explains delimited versus fixed-width versus structured formats in plain words. It covers header and trailer records, control totals, quoting and escaping realities, and versioning the format from day one.
• Acknowledgment Patterns: Knowing the Other Side Got It
  This article covers ack files, control totals, receipt semantics, and reconciliation reports - what each proves and what silence should mean. It explains how to choose the lightest pattern that ends the did-you-get-it calls.
• Error Handling Across a File Interface
  This article covers rejects and reject files, partial batches, and reprocessing coordinated between two teams. It covers the shared evidence trail that settles whose side failed without a meeting.
• Evolving a File Interface Without Breaking the Other Side
  This article covers adding fields, changing formats, and renaming safely. It explains version markers, parallel-run migrations, deprecation windows, and the coordination playbook for interfaces with many consumers.

Explore More Topics

This series is part of the Sysax file transfer topic library. The library covers the protocols, security practices, automation techniques, and operational skills behind reliable file transfer. The library pairs well with the practical tools we build. Sysax Multi Server is a secure FTP, FTPS, SFTP, and HTTPS server for Windows. Sysax FTP Automation schedules and scripts secure transfers so the routine ones run themselves.