myTRAC Rate

This endpoint allows permissioned users under TRAC contributor Organizations to call and return the SONAR myTRAC rates based on their Organization’s TRAC data. Our rate data is updated daily, to produce the myTRAC rate we use a 14 day lookback period for all the load transactions within a contributor's data to get them their benchmark rate on the lane vs the rest of the consortium. If there aren’t at least 3 load transactions in that lookback we then use 90 days, if there aren’t 3 load transactions in that time period we can’t produce a rate and you will receive a 204 No Content response.

OD pairs are defined by Zip3’s with Van and Reefer being the two equipment types currently supported now, with plans to add Flatbed in the future. Multiple lanes can be sent in a single request. You can click on the Body Sample to the right to populate the example in the test body below.

For more information about getting access to this endpoint or using this endpoint, please reach out to our Customer Success team (cs@gosonar.com). To become a TRAC contributor, email bd@gosonar.com.

This endpoint handles the following input fields:

• date: the date for which the myTRAC rate is being requested.(YYYY-MM-DD); required
• origin: the postal/zip code for the origin point including leading zero(s); the first three digits of the zip code are all that is required and currently used, but the full zip code is accepted; required
• destination: the postal/zip code for the destination point including leading zero(s); the first three digits of the zip code are all that is required and currently used, but the full zip code is accepted; required
• equipment_type: will be ‘VAN’ or ‘REEFER’; required
• lane_id: a unique identifier set by the client and will be returned with the response; optional

​Here are the output fields returned in a successful call:

• successful_lane_responses: A list object that contains the output information associated with the valid requested lanes.
• lane_id: the unique identifier provided in the request by the client for the lane.
• od_pair: the origin and destination zip3 pair for the lane (i.e. 606-303)
• origin: the origin provided for the lane.
• destination: the destination provided for the lane.
• current_trac_miles: the TRAC effective miles for the lane.
• current_trac_rpm_adj: the TRAC RPM, adjusted to the client’s average mileage.
• current_trac_rate_adj: the TRAC Rate, adjusted to the client’s average mileage.
• avg_diff_rpm: the average difference between TRAC RPM and the client’s RPM.
• avg_diff_rate: the average difference between TRAC Rate and the client’s Rate.
• avg_miles: the client’s average miles on the lane.
• lookback: the number of days used as a lookback period for a client’s TRAC load transactions to derive the myTRAC rate. This will be 14 days if a minimum of 3 transactions are found, if not it will back out to 90 days with the same 3 transaction minimum.
• num_transactions: the number of load transactions found in the lookback period used to derive the myTRAC rate for the lane.
• my_trac_rate: the client’s myTRAC flat rate for the lane derived from the load transactions found in the lookback period.
• my_trac_rpm: the client’s myTRAC rate per mile for the lane derived from the load transactions found in the lookback period.
• data_timestamp: the date in the request for the myTRAC rate.
• generated_on: the date the myTRAC rate for the lane was calculated on.