POST /api/truckstop/loads/count
Price: 1 credit
How many truckloads the Truckstop load board holds picking up in a US state or Canadian province, or around a city in it, for one equipment type.
Use it to size or compare freight markets, for example van loads out of Chicago against Dallas. Equipment groups overlap on the board, so the counts of flatbed, van and reefer do not add up to any.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)origin_state string required — Two-letter US state or Canadian province code of the pickup (examples: "IL"; pattern: ^[A-Za-z]{2}$)origin_city string nullable — Pickup city inside origin_state; loads are then matched around that city (examples: "Chicago"; minLength: 1)equipment string required — Truck equipment type (one of: "any", "flatbed", "van", "reefer", "specialized", "hot_shot"; examples: "van")@type string (default: "TruckstopLoadCount")origin_state string requiredorigin_city string nullableequipment string requiredload_count integer required422 — 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 — Truckstop could not locate origin_city in origin_state; check the spelling or search by state only. 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.