/thomasnet/categories

POST /api/thomasnet/categories

Price: 1 credit

Browse the Thomasnet product taxonomy. Without a category, returns the top-level industry categories; with a category url slug, returns that category's sub-categories and product headings (each with a supplier count and the heading id used by supplier search).

How to use it

Browse the Thomasnet category tree. Pass no category to list top-level industry categories, or a category url slug (e.g. pumps-valves-accessories) to expand it. Returns id, name, url_slug, description, category_count, heading_count, sub_categories (id/name/url_slug/category_count) and headings (id/name/natural_name/url_slug/company_count). Heading ids feed thomasnet/companies/search heading_id.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• category string nullable — Category url slug to expand (returns its sub-categories and product headings). Omit to get the top-level industry categories. (examples: "pumps-valves-accessories", "custom-manufacturing-fabricating")

Response

• @type string (default: "ThomasnetCategory")
• id string nullable
• name string nullable
• url_slug string nullable
• description string nullable
• category_count integer nullable
• heading_count integer nullable
• article_count integer nullable
• whitepaper_count integer nullable
• sub_categories array (default: [])
  • @type string (default: "ThomasnetSubCategory")
  • id string nullable
  • name string nullable
  • url_slug string nullable
  • description string nullable
  • category_count integer nullable
• headings array (default: [])
  • @type string (default: "ThomasnetCategoryHeading")
  • id string nullable
  • name string nullable
  • natural_name string nullable
  • url_slug string nullable
  • company_count 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 — Category not found (unknown url slug) 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.