/dat/trendlines/market-trends

POST /api/dat/trendlines/market-trends

Price: 1 credit

The current DAT Trendlines weekly market snapshot: the national diesel price and the week-over-week, month-over-month and year-over-year percent changes in load postings, truck postings, fuel price, and the spot rate and load-to-truck ratio of vans, flatbeds and reefers.

How to use it

Use it for a one-call read on the direction of the US truckload market this week. The changes are percentages only; for the rate and ratio levels call dat/trendlines/rate-history and dat/trendlines/load-truck-ratios.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)

Response

• @type string (default: "DatMarketTrends")
• fuel_price_date string nullable
• fuel_price_per_gallon_usd number nullable
• load_postings_change_week_over_week_percent number nullable
• load_postings_change_month_over_month_percent number nullable
• load_postings_change_year_over_year_percent number nullable
• truck_postings_change_week_over_week_percent number nullable
• truck_postings_change_month_over_month_percent number nullable
• truck_postings_change_year_over_year_percent number nullable
• fuel_price_change_week_over_week_percent number nullable
• fuel_price_change_month_over_month_percent number nullable
• fuel_price_change_year_over_year_percent number nullable
• equipment_trends array (default: [])
  • @type string (default: "DatEquipmentTrend")
  • equipment string required
  • spot_rate_change_week_over_week_percent number nullable
  • spot_rate_change_month_over_month_percent number nullable
  • spot_rate_change_year_over_year_percent number nullable
  • load_to_truck_ratio_change_week_over_week_percent number nullable
  • load_to_truck_ratio_change_month_over_month_percent number nullable
  • load_to_truck_ratio_change_year_over_year_percent number nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.