Our Web API endpoints give external applications access to Spring Systems transactional data.
Usage of web API’s is much preferred over file based integration. For file based integration please see our default EDI specifications or email sales to discuss other formats.
While most transactions are supported in both directions, we find it most efficient for the transaction
originator to initiate the call.
For example, while we support an external party calling into our system to ‘Get Ship
Request (940) from Spring’, we have found it faster and more efficient for our system to instead push
the Ship Request (940) out to the receiving system (e.g. your WMS). Our system is the originator of the
Ship Request (940) transaction so it is faster if we immediately push it out to the WMS (warehouse
management system). Similarly, we prefer for the WMS to push back to us the completed shipment.
This guide details your system calling Spring Systems' PortalApp endpoints to read, create, or update transactions and obtain shipping documents, however the same functionality and data structures also apply when Spring Systems is pushing data to your system. Please contact your project team or email support to discuss having Spring Systems' PortalApp push data to your system.
This guide details PortalApp default data structures however custom mapping is available to work with other data structures and formats (additional fees may apply). Once again, please contact your project team or email support to discuss.