All applications using Connexion must be certified before interacting with the production DAT Loadboards network, RateView data, or other DAT application. DAT Solutions has the right to approve or prohibit any use of Connexion at the sole discretion of DAT Solutions.

Applications must supply a unique identifier to the interface. The identifier is specified in the thirdPartyid field of Login Request in the interface. In the SDK, the thirdPartyId field is accessed through the TFMI_Session object property “application”.

Applications must not use the interface for data mining of the DAT database, analytics, or purposes other than posting or finding available trucks or loads. Any planned use of the interface, other than posting or searching for available trucks or loads, must be specifically approved by DAT Solutions.

Each user of the application must be a separate Connexion user and have their posts and searches performed by that Connexion user. This requirement allows for better interaction with DAT Solutions applications.

All applications that support searching for loads must also support posting using Connexion for loads and/or trucks as appropriate for the customer. Any application that posts loads or trucks to the DAT Load Board database and uses Connexion for any other functionality, such as looking up the government safety and authority data for a carrier using DAT CarrierWatch®, must post using Connexion.

DAT Solutions may provide different pricing for post-only applications compared to post and search applications.

Applications must not re-post or post the same asset again without changes to the posting. DAT Solutions has “refresh” facilities that update the time stamp on Connexion postings at intervals so they do not appear stale. The application must not implement its own facilities to get a later time stamp.

A post-only application must not support alarm match. Applications supporting alarm match must provide a search facility.