Sign inGet started

rackspecs API

A REST API over the normalized catalog: discover the queryable fields for a category, filter products by spec, fetch a single product, and poll a change cursor to keep your own feed in sync. JSON over HTTPS.

Base URL: https://api.rackspecs.com

Authentication

Every request needs an API key. Create one on your account page (requires an active API subscription) — the key is shown once, so store it securely. Send it on each request as either header:

# Either of these works:
curl -H "Authorization: Bearer rsk_live_xxx" https://api.rackspecs.com/api/pdus/schema
curl -H "X-API-Key: rsk_live_xxx"            https://api.rackspecs.com/api/pdus/schema

A missing or revoked key returns 401; a valid key without an active API subscription returns 402. Keys can be revoked anytime from your account.

Quickstart

1. Discover what you can filter on. 2. Filter the catalog. 3. Fetch a product.

KEY=rsk_live_xxx

# 1) What fields can I query for rack PDUs? (types, units, value ranges)
curl -H "Authorization: Bearer $KEY" https://api.rackspecs.com/api/pdus/schema

# 2) Three-phase PDUs with at least 30 outlets
curl -H "Authorization: Bearer $KEY" \
  "https://api.rackspecs.com/api/pdus?filter=input_phases:3&filter=outlet_count:>=:30&limit=50"

# 3) One product by its catalog path
curl -H "Authorization: Bearer $KEY" \
  https://api.rackspecs.com/api/pdus/eaton/epdu-g4-cn

Endpoints

GET/api/categories

List catalog categories. The 13 category slugs: pdus, transfer-switches, enclosures, cooling, busway, kvm, cabling, gpus, servers, storage, interconnect, memory, switches.

GET/api/{category}/schema

Discover the queryable surface. Returns every field with its type, unit, coverage, and value distribution (enum values + counts, or numeric min/max/median) plus a copy-paste filter example — so you never have to guess field names. Also lists the captured long-tail spec labels.

GET/api/{category}

List + filter products in a category. Query params:

  • filter=field:value or filter=field:op:value — repeatable. Ops: =, !=, >, <, >=, <=, in (e.g. filter=phase:in:1-phase,3-phase).
  • q= — case-insensitive full-text search; all terms must match.
  • vendor_id= — restrict to one vendor (key-efficient).
  • limit= 1–500 (default 100), cursor= — opaque pagination token from the previous response's next_cursor.

Use /schema to find valid field names + units before filtering.

GET/api/{category}/{vendor_id}/{product_key}

Fetch one product by its catalog path. Returns the full normalized spec set + a provenance map (datasheet_url, fetched_at).

GET/api/{category}/facets

{ field: { value: count } } over the faceted fields — useful to build a filter UI or see the value distribution at a glance.

GET/api/changes/{category}

The change cursor. since=<ISO-8601> returns items with last_changed_at > since, newest-tracked first, with limit + cursor pagination. This is how you keep a local copy in sync without re-pulling the catalog.

Keeping a feed in sync

Bootstrap once by paging the full category, then poll the change cursor for just what moved since your last timestamp.

# Bootstrap: page the whole category
curl -H "Authorization: Bearer $KEY" "https://api.rackspecs.com/api/servers?limit=500"
# ...follow next_cursor until it's null, recording the latest last_changed_at.

# Steady state: poll only what changed since your watermark
curl -H "Authorization: Bearer $KEY" \
  "https://api.rackspecs.com/api/changes/servers?since=2026-06-09T00:00:00Z&limit=500"

Provenance

Every product carries the manufacturer datasheet it was extracted from (provenance.datasheet_url) and when it was fetched. Verify against the source before purchase — values are transcribed from published datasheets.

Need a key or a plan? See API plans · Manage your keys · Contact us

API documentation | rackspecs