6.8.8. How to Integrate with Dayton Freight?

This "How to" should provide you with the necessary steps to implement a working integration with Dayton Freight from scratch using Babelway.

Figure 6.48. 


Preferred Protocols and Message Formats. When integrating with Dayton Freight, you will be expected to send X12 (version 4010 or above) messages through FTP, AS2, or VAN.

Contact and Resource information. 

Integration Flow Request

To request the setup of an automated document transfer with Dayton Freight you will be requested to complete the following form. You can find the forms on their website (see contact information) and in Babelway's resources: request and specifications. Note that we advise you use AS2 as a communication method since it is the cheapest (VAN involves additional costs) and most secure.

Figure 6.49. 


For invoices Dayton Freight requires the use of acknowledgements. Babelway supports sending 997s direction upon message reception.

Figure 6.50. 


Setting up your connection

You can set up a number of connections with Dayton Freight since they support FTP, AS2 and VAN. We discourage the use of VAN as it involves additional costs and is the least straightforward setup. We will describe the setup using an AS2 connection which is the most secure protocol. Your channel will look something like this:

Figure 6.51. 


Once you have indicated to Dayton Freight that you will be integrating using AS2 they will expect you to share your AS2 information. In order to provide this, you can begin by creating a dummy AS2 gateway in:

Figure 6.52. 


Download the AS2 specifications ZIP in the properties tab of your newly created gateway. It contains all you will need to provide Dayton Freight. Note that Babelway supports multiple signing and encryption algorithms. The default values are highlighted below:

Figure 6.53. 


You will need to receive from Dayton Freight the following information to complete your configuration:

  1. The AS2 ID Dayton Freight will use to receive/send your content
  2. The address of the AS2 server Dayton Freight will be expecting your content to reach
  3. The certificate you need to use to encrypt your content

You will use this information to create your gateway out (note that Dayton Freight requires you use SHA1 encryption - make sure to update it in the properties tab of your gateway):

Figure 6.54. 


And complete your gateway in:

Figure 6.55. 


Configuring your messages

If you implement the invoice flow (X12 210), you will be required to send out 997 acknowledgements. Additionnally for documents you send them you may request to receive a 997 acknowledgement in return which you may want to correlate with your original messages. In both cases, you should have a look at Babelway's 997 implementation:

Figure 6.56. 


This documentation is based on our integration projects but we'd love to enhance and update it with your own feedback and experience: support@babelway.com.

Last update: June 06 2018