Thomasnet supplier search

GET https://api.api.sh/thomasnet/v1/search
1 credit / call jobs & b2b try it in the playground →

Industrial suppliers on Thomasnet for a product or service: id, name, profile link, description, supplier type (manufacturer, distributor, service company...), tier, phone, website, logo, employees, annual sales, year founded, address with coordinates, capabilities (materials, industries, production scale), categories, products and videos; plus the matched category, related categories, the total number of suppliers and the site's filter options with counts. Returns the first 25 suppliers (the site shows later pages to signed-in users only); narrow with region. Narrow with the site's own filters: supplier validation, video type, catalogs, production scale and brand (values from filters of an unfiltered search); several values of one filter must all match. applied_filters echoes them.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
qrequired string Product or service, e.g. cnc machining, valves, injection molding. Example: cnc machining
region string Region name as Thomasnet writes it, e.g. northern-ohio, southern-california, texas-southern, new-york-city; needs a q that matches a supplier category.
supplier_validation string thomas_verified, thomas_registered or xometry_verified; comma-separated for several.
video_type string Suppliers with a video of this type: factory_tour, company_overview, product_spotlight or project_spotlight.
catalogs string Suppliers with catalogs: any, product_catalogs, capabilities_profile or line_card.
production_scale string Production scale, comma-separated: High Volume, Long Run, Low Volume, Production Runs, Prototype, Short Run, Small Batch, Toll.
brand string A brand from the Brands filter, e.g. Haas.

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/thomasnet/v1/search?q=cnc+machining" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.