/tractorsupply/stores

POST /api/tractorsupply/stores

Price: 5 credits

Find the Tractor Supply stores nearest to a US ZIP code with address, hours, services and distance

How to use it

Returns Tractor Supply stores ordered by distance from the ZIP code, each with its store id and price zone. Pass the same ZIP code to the product endpoints to get that area's prices and stock.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• zip_code string required — US ZIP code to find the nearest stores to (examples: "08085", "75001")
• count integer required — Max number of stores to return (min: 1; max: 100)

Response

• @type string (default: "TractorsupplyStore")
• id string required
• name string nullable
• address string nullable
• city string nullable
• state string nullable
• zip_code string nullable
• country string nullable
• phone string nullable
• latitude number nullable
• longitude number nullable
• distance_miles number nullable
• time_zone string nullable
• price_zone string nullable
• hours_today string nullable
• opening_hours array (default: [])
  • @type string (default: "TractorsupplyStoreHours")
  • day string required
  • hours string required
• services array (default: [])
• is_pickup_available boolean nullable
• is_same_day_delivery_available boolean nullable
• is_standard_delivery_available boolean nullable
• is_parcel_delivery_from_store_available boolean nullable
• drive_thru_pickup_side string nullable
• is_aisle_info_available boolean nullable
• is_active boolean nullable

Errors

• 422 — No Tractor Supply store was found for this ZIP code. 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.