/dat/trendlines/rate-history

POST /api/dat/trendlines/rate-history

Price: 1 credit

National average truckload rate history from DAT Trendlines for one equipment type, spot or contract, monthly or weekly, in the US or Canada, newest period first.

How to use it

Use it to chart how national van, flatbed or reefer rates moved over time or to compare spot against contract pricing. The rate DAT displays on its site is rate_usd plus fuel_surcharge_per_trip_usd.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• equipment string required — Truck equipment type (one of: "van", "flatbed", "reefer"; examples: "van")
• rate_type string required — spot for the spot market, contract for contracted rates (one of: "spot", "contract"; examples: "spot")
• period string required — month for the monthly series, week for the weekly series (one of: "month", "week"; examples: "month")
• country string required — Market country (one of: "us", "ca"; examples: "us")
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "DatRate")
• equipment string required
• rate_type string required
• country string required
• period string required
• period_start_date string required
• year integer nullable
• month integer nullable
• rate_usd number nullable
• fuel_surcharge_per_trip_usd number nullable
• rate_calculated_at integer 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.