Skip to content
Argos Software

API and data integration

Argos API and data integration

Get data into and out of Argos without keying it twice. Integration endpoints take receivables data, and mapped flat files and XML carry orders, receipts and inventory between Argos and your other systems on a schedule.

Request a demo
Network cables and a server rack

What the Argos API and file exchange cover

  • AR integration endpoints create a cash receipt with its applications and payments, or apply a customer payment to open invoices oldest first, validating every code.
  • The same AR API creates open items with their GL distribution lines and looks up a customer's open items and transactions.
  • Purchase orders and receipts arrive from external systems as XML, and XML delivery, goods receipt and inventory messages convert to flat files and back.
  • Import and export maps for delimited and fixed-width flat files use lookups and translation tables to turn another system's codes into yours.
  • Imports, exports and FTP transfers run as scheduled jobs, and EDI moves with each trading partner over FTP, email, shared folders or a network provider.
A team collaborating around a table in an office

Integration capabilities

Every connection rests on the same exchange, mapping and monitoring tools Argos uses for EDI.

Automated EDI and File Exchange

Run partner EDI and file exchange automatically

Inbound EDI and flat files are picked up automatically, answered with 997 acknowledgements and committed straight into your warehouse, order and inventory records. Outbound documents queue as soon as the source records change and go out to each partner on a schedule.

  • Receive inbound EDI, match it to the right trading partner and send 997 functional acknowledgements
  • Commit mapped inbound EDI and flat files into your warehouse, order, inventory and other records
  • Queue outbound EDI when source records change, and assemble it for each trading partner

EDI and Flat File Mapping

Map partner EDI and flat files to your data

Build import and export maps for EDI and for delimited or fixed-width flat files, with lookups and translation tables that turn a partner's codes into yours.

EDI Message Monitoring and Resubmission

Track every partner message and fix failures

Search inbound and outbound EDI and flat file messages by partner, transaction set, status and date, and see where each EDI transaction set stopped: parse, mapping or commit.

Built around your systems

Each integration is scoped with you during implementation: which records move, which format each system speaks and how often files run. Maps are assigned to each trading partner and delivery destination.

Inbound and outbound EDI and flat file messages land in a searchable history, and an inbound document can be resubmitted once the problem is fixed.

Implementation servicesERP and accounting integration

A consultant leading a planning workshop at a whiteboard

Argos API questions

Straight answers, drawn from what the software does today.

Does Argos have an API?

Argos has integration endpoints for accounts receivable: creating cash receipts, applying customer payments and creating or searching open items. Other data moves by mapped flat files and XML.

Which file formats can Argos import and export?

Delimited and fixed-width flat files and EDI, through import and export maps set up for the system on the other end, and XML for purchase orders, receipts, and delivery, goods receipt and inventory messages.

How do files reach Argos?

Imports, exports and FTP transfers run as scheduled jobs, and EDI moves with each partner over FTP, email, shared folders or a network provider. Messages are logged for search, and a failed inbound document can be resubmitted.

Related areas

More integration pages

Map your integration

Talk through the systems you run and how Argos would connect to each, with the Argos team.

Request a demoSee all features