Public API for custom wire harnesses

MiniProto is a US custom wire-harness and cable-assembly manufacturer in Kingston, NY.

This API lets a program or an LLM look up real connectors, wire families, and lead times, validate a harness spec, and get a real price.

It does not place orders. There is no create_order endpoint. Checkout happens on miniproto.com, and a human confirms the order.

To choose ConfigV2 versus a drawing RFQ, see /guides/configure-vs-send-a-drawing. For the fields a harness RFQ should include, see /guides/what-to-put-in-a-harness-rfq.

The one call that matters is POST /api/v1/price-snapshots. Send connectors by manufacturer part number (MPN). You do not need to look up a UUID first.

A 12-pin Deutsch DTM pair has 12 circuits. This example sends two wires; the other ten are elided.

The response is a signed price snapshot. Shape:

POST /api/v1/quotes and GET /api/v1/quotes/{id} are live and require MiniProto customer credentials. Reads plus POST /api/v1/validations and POST /api/v1/price-snapshots are anonymous. A price snapshot saves one seven-day configurator design (the continueUrl handoff) — its only side effect — and creates no quote, no order, and no reservation. Writes are not bot-gated as a substitute for auth. OpenAPI names the quote-route schemes CustomerOAuth and CustomerApiKey; both are live on the quote routes.

Configurator flow: read GET /api/v1/connector-families, GET /api/v1/connectors, GET /api/v1/wires, and GET /api/v1/lead-times, copy family, gauge, and colour values verbatim into the spec, then POST /api/v1/validations, then POST /api/v1/price-snapshots. The anonymous snapshot response adds resolvedSpec, assumptions, and an absolute seven-day continueUrl that opens the saved design at /configuratorV2?d=<id>. That saved design is the snapshot's only side effect; it creates no quote and no order. Only when MiniProto customer credentials are available, finish with authenticated POST /api/v1/quotes sending the returned priceToken.

RFQ flow: authenticated POST /api/v1/quotes with a written description plus PDF/PNG/JPEG files up to 10MB for engineer review.

GET /api/v1/connectors accepts these query parameters: mpn, family, pinCount, q, limit (integer 1–100, default 25), and offset (integer ≥ 0, default 0). q is free-text search across MPN and description. An unknown query parameter — including search — returns 400 INVALID_INPUT rather than being ignored.

POST /api/v1/validations and POST /api/v1/price-snapshots take { "spec": <harness spec> }. The machine-readable JSON Schema is at /docs/api/schema.json.

• connectors[] — minimum 2, maximum 16. Each item has ref and side. ref is either { "mpn": "..." } or { "componentId": "..." }, never both. side defines wire direction: wires run from a left connector (sourceConnector/sourcePin) to a right connector (targetConnector/targetPin). Same-side or right-to-left is 422 DESIGN_INVALID.
• wires[] — minimum 1, maximum 500. A pin-to-pin end uses sourceConnector/sourcePin or targetConnector/targetPin. A splice end uses sourceSplice or targetSplice (0-based index into splices[]). Each end is one or the other, not both. Each wire also has gauge, color, wireFamily, and lengthMm (maximum 10000 mm / 10 m). wireFamily and color must be copied from GET /api/v1/wires. The canonical gauge form is "18 AWG".
• splices[] — optional, maximum 50. Each item may set method to "solder" or "crimp".
• quantity — order quantity used for the price. Defaults to 1. Maximum 1000. Larger runs need engineer review.
• projectName and designNotes — optional strings.
• wireProfile — optional. Set it to "standard-automotive" to omit wireFamily, gauge, and color on wires; the API fills them with GXL, 18 AWG, and deterministic per-wire colours (Black, Red, White, Green, Blue, Yellow, Orange, Violet, brown, Gray, repeating by wire index). Explicit values always override the profile. Every value the profile supplied is reported in the response's assumptions entries ({ path, value, source }, where source is "standard-automotive"), and the fully explicit normalized spec comes back as resolvedSpec. Without the profile, wireFamily, gauge, and color are required on every wire.

A spec that fails schema checks is 400 INVALID_INPUT. A spec that is schema-valid but cannot be built is 422 DESIGN_INVALID from POST /api/v1/validations and POST /api/v1/price-snapshots.

Copy wireFamily, gauge, and color from GET /api/v1/wires → wireFamilies. Colours are listed per gauge (gauges[].colors), not as a sibling of gauges and not as a family-level colors array, because a family stocks different colours at different gauges — GXL has 11 colours at 8 AWG and 27 at 20 AWG. Pick a gauge first, then a colour from that gauge's list. Combining a family-level colour with an arbitrary gauge is rejected.

A wires[] entry built from that excerpt:

The canonical gauge spelling is "18 AWG". These spellings are also accepted and resolve to that form: "18", "18awg", "18 gauge", "18 ga", "#18", and "AWG18". Anything else is rejected with a DESIGN_INVALID 422 that names the accepted values.

A complete minimal valid spec:

A connector ref may be an MPN or a componentId. Exact MPN match wins because MPNs are unique in the catalog.

If exact match misses, lookup falls back to search.

• Zero matches → 404 UNKNOWN_CONNECTOR.
• More than one match → 409 AMBIGUOUS_MPN. The errors field is the candidate array. Pick one and retry with componentId.

Ambiguous response:

A price token is a stateless signed snapshot of a price for a specific BOM, quantity, and price version. It is not an order and not a reservation of parts or capacity.

• priceToken — HMAC signature over the snapshot payload.
• priceVersion — pricing ruleset id. Current value: v1-2026-08-20.
• expiresAt — 7 days after issuance.
• unitPriceCents — customer unit price in cents.
• setupFeeCents — setup fee in cents.
• totalCents — quantity × unit price, plus setup fee, in cents.
• priceBreaks[] — quantity tiers with unitPriceCents and totalCents.
• bomHash — SHA-256 hex of the canonical spec JSON.
• currency — always USD. quantity is spec.quantity. resolvedConnectors repeats catalog resolution. leadTime is { tier, businessDaysMin, businessDaysMax } for the selected manufacturing lead-time tier, or null if none is resolvable. tier is a value from GET /api/v1/lead-times → leadTimes[].tier. Bounds are business-day counts, or null when unknown.
• resolvedSpec — the fully explicit normalized harness spec actually priced: caller-supplied values plus anything wireProfile: "standard-automotive" filled in.
• assumptions[] — one { path, value, source } entry for every value the API chose on the caller's behalf; source is "standard-automotive" when the wire profile supplied it, and the array is empty when nothing was defaulted.
• continueUrl — absolute URL that opens the saved design in the visual configurator at /configuratorV2?d=<id>; it stays valid for the token's seven-day life. That saved design is the snapshot's only side effect: it creates no quote, no order, and no reservation.

A token is required later to create a draft quote with authenticated POST /api/v1/quotes. A stale token is rejected with PRICE_EXPIRED.

Errors use RFC 9457 problem details. The Content-Type is application/problem+json. Branch on code, not on title.

type is https://www.miniproto.com/docs/api#error- plus the kebab-case code. Example: AMBIGUOUS_MPN → https://www.miniproto.com/docs/api#error-ambiguous-mpn.

Problem document:

Limits are per IP: 120 reads/min and 20 writes/min. GET routes use the read bucket. POST /api/v1/validations and POST /api/v1/price-snapshots use the write bucket.

Successful and error responses include RateLimit-* headers. A 429 also includes Retry-After.

Browser clients are supported. /api/v1 answers OPTIONS preflight with 204 and sends Access-Control-Allow-Origin: *, Allow-Methods: GET, POST, OPTIONS, and Allow-Headers: Authorization, Content-Type, Idempotency-Key. Do not send cookies; use a Bearer token when a route requires auth.

Price scraping is an abuse case, not a feature.

Send Idempotency-Key on POST requests.

A replay of the same key, route, and body returns the original response with Idempotency-Replayed: true.

Reusing a key on the same route with a different body is 409 IDEMPOTENCY_CONFLICT.

• No agent-placed orders. There is no create_order.
• No connector families outside the digitised catalog. See GET /api/v1/connector-families.
• Harnesses are 2 to 16 connectors and up to 500 wires per spec.
• No minimum order quantity. Maximum order quantity is 1000; larger runs need engineer review.