Skip to content
Developers · AI agents · Integrators

The RobbJack catalog, as an API.

Search every standard RobbJack tool by part number or by specs and get JSON back — geometry in ISO 13399 codes, list prices, live availability and CAD links. Read-only, no key, no sign-up.

Endpoints

Base URL https://robbjack.com. All responses are JSON unless noted. Machine-readable contract: OpenAPI 3.1.

What a search result contains

toolNumber, name, description
The catalog's own description — the same text as the tool page.
specs[]
ISO 13399 code, label, and the value in inches and millimeters (angles in degrees).
parts[]
Every orderable finish: part number, coating, priceUsd (US list / trial-tool retail), gtin12 (only when its GS1 check digit is valid), live availability and, when on the shelf, quantityOnHand.
partNumberMatch
Set when q is an orderable part number — the exact part and its page.
url, isoJson, cad.dxf
Links to the tool page, its ISO 13399 JSON and its DXF.

Fair use

Search allows 60 requests per minute per IP — far more than an agent conversation or a CAM import needs. Over the limit you get HTTP 429 with a Retry-After header. Need the whole catalog? Download it in one file instead: master catalog JSON/CSV.

What the data means

Prices are US list prices in USD for direct trial-tool purchases; production quantities are sold through authorized distributors. Availability is the live ERP tier, refreshed every 15 minutes. Speeds & feeds are starting points — see each tool page.

Partner API (keyed)

For distributors, reps and integration partners

The same public catalog data as the anonymous API, plus starting speeds & feeds, cross-reference, change tracking, STEP solids and the merchant feeds — behind a key with per-key quotas, so a partner can build a real integration (a catalog mirror, a punchout lookup, an embedded finder) without sharing a public rate limit. Base URL https://robbjack.com/api/v1. Contract: OpenAPI 3.1.

Getting a key
Keys are issued through the Partner Access Program — ask your RobbJack rep. A secret key (rj_live_sk_…) is for your servers; a site key (rj_live_pk_…) is for a browser page and works only from the website origins bound to it. rj_test_… twins return the same data and are flagged as test traffic. The key is shown once at issue; rotation keeps the old key alive for 30 days.
Sending it
Secret keys: Authorization: Bearer rj_live_sk_… — never in a URL. Site keys: ?k=rj_live_pk_… (or header X-RJ-Key) from an allowed origin; CORS answers only that origin. Every error is JSON { error, code, docs } with a 401 / 403 / 429 / 503 status.
Scopes
catalog:read search, tools, parts, ISO, changes · stock:read availability labels · crossref:read competitor cross-reference · sf:read starting speeds & feeds · cad:read DXF + STEP · feed:read merchant feeds and the Partner Data Pack · embed the co-branded storefront. New keys carry catalog + stock; ask your rep for more.
Quotas (per key)
Catalog, stock, cross-reference and speeds & feeds: 30 per 10 s, 3,000 per hour, 20,000 per day. CAD: 5 per 10 s, 120 per hour, 500 per day. Feeds and Data Pack files: 30 per hour, 120 per day. Site keys add 600 per hour per origin. Over a quota you get HTTP 429 with Retry-After; GET /api/v1/me shows your scopes and usage. Need the whole catalog? Use the Data Pack or /api/v1/changes?since= — not a crawl.
  • GET /api/v1/search?q=3/8 4 flute AlTiN&limit=25&page=1
  • GET /api/v1/tools/FM-201-12-BN
  • GET /api/v1/parts/fmhv30224
  • GET /api/v1/changes?since=2026-10-01
  • GET /api/v1/iso?tool=FM-201-12-BN&format=json
  • GET /api/v1/cad?tool=FM-201-12-BN&format=step
  • GET /api/v1/crossref?brand=harvey&part=54212
  • GET /api/v1/sf/FM-201-12-BN
  • GET /api/v1/feed?format=google
  • GET /api/v1/me

List prices only. The Partner API serves US list prices and list quantity breaks — never a partner’s net pricing, never another customer’s data. Availability shows exact counts from 1 to 9 and “10+” above. A part that is no longer offered answers 404 like an unknown number. Breaking changes ship as a new major version; a retiring version carries Deprecation and Sunset headers for at least 12 months.

For AI assistants and crawlers

  • /llms.txt maps the site, the data files and these endpoints.
  • Tool pages carry Product / ProductGroup JSON-LD with typed ISO 13399 specs, every finish as a variant, prices and live stock.
  • Search and part-number cross-reference work without JavaScript: /tools?q=3/8 4 flute AlTiN and /cross-reference?brand=harvey&part=<their part number>.
  • Shopping feeds (every orderable part, refreshed every 6 hours): Google / Microsoft Merchant XML and OpenAI JSON Lines (gzipped).
  • robots.txt allows these API paths; the rest of /api/ (checkout, accounts, portal) stays private.

Questions or a bigger integration (EDI, punchout, a distributor feed)? Contact RobbJack.