Developer documentation

Build against source-backed technical data.

Use the versioned API to search products, inspect provenance, compare normalized specifications, and read immutable revision history. Values are evidence-bearing data, not installation approval.

Authentication

Scoped bearer keys

Create a key in the developer portal. Store the secret server-side and send it only over HTTPS.

curl https://datasheets.jit.ng/api/v1/products \\n  -H "Authorization: Bearer jdc_…"

Use the smallest required scope: products:read, search:read, or revisions:read.

Collections

Stable pagination and projection

Collections accept limit, opaque cursor, sort, and comma-separated fields. The response returns meta.next_cursor when another page exists.

GET /api/v1/products?limit=10&sort=model&fields=id,model,specs

Metering

Plan-aware responses

Bearer requests return request, timing, rate-limit, and quota headers. A request over the rate limit returns 429; a request without sufficient credits returns 402.

X-Request-Id
X-RateLimit-Remaining
X-Quota-Balance
X-Quota-Cost

Trust boundary

Provenance is part of the data

Read the source, revision, claim snapshots, and source locators before using a value in a safety-critical workflow. Verify against manufacturer documentation and applicable electrical codes.

Open the full OpenAPI contract →