repairOrder
The repairOrder noun — identity, lifecycle, events, and every capability as an anchored section: 3 capabilities, 0 live, 3 sandbox, 0 declared.
repairOrder is one of the estate's 317 automotive nouns — a job a car needs done. It carries 3 capabilities: 0 live, 3 sandbox, 0 declared · doors aggregator.vin.
Identity
| Noun | repairOrder |
| Pillar | Services (facets: 3 services) |
| Capabilities | 3 — 0 live · 3 sandbox · 0 declared |
| Entities | RepairOrder |
| Doors | aggregator.vin |
| SDK | Vin.repairOrder.* from apis.vin |
| Address | /catalog/repairOrder#{action} — the anchor IS the wire name minus repairOrder. |
Lifecycle
RepairOrder — RepairOrderFSM: 7 states, 8 transitions — Open · InProgress · AwaitingParts · EstimateApproval · Completed · Invoiced · Closed. Each transition is a past-tense event on the record.
Events
The vocabulary this noun can append to the record — 3 past-tense, versioned event types, each linked to the capability that emits it:
RepairOrder.closed@1— emitted bycloseRepairOrder.opened@1— emitted byopenRepairOrder.started@1— emitted bystart
Apply & book
open
repairOrder.open · POST /repair-orders/open · gate key · sandbox · answers RepairOrderOpen@1
No input — this capability takes no request body.
Door — aggregator.vin serves this noun on its two routes: / (the landing) · /1C4RJFBG4LC317588 (the VIN lens).
Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.
Emits — RepairOrder.opened@1.
import { repairOrder } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await repairOrder.open()curl -X POST https://apis.vin/repair-orders/open \
-H 'content-type: application/json' \
-d '{}'Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.
{
"type": "OK",
"answers": "RepairOrderOpen@1",
"value": {
"vin": "1HGCM82633A004352",
"noun": "repairOrder",
"asOf": "2026-08-10",
"id": "RO-1f2a3746",
"concerns": [],
"payType": "warranty",
"lines": [
{
"line": 1,
"kind": "labor",
"description": "labor operation",
"amountCents": 16500
}
],
"technicianId": "TECH-3f68cc26",
"estimateId": "EST-feef6ee9",
"status": "Open",
"ticket": {
"roId": "RO-1f2a3746",
"position": "Open",
"standing": "open",
"basis": "one-ticket-read-never-advanced"
}
},
"evidence": {
"vin": "1HGCM82633A004352",
"noun": "repairOrder",
"asOf": "2026-08-10",
"id": "RO-1f2a3746",
"concerns": [],
"payType": "warranty",
"lines": [
{
"line": 1,
"kind": "labor",
"description": "labor operation",
"amountCents": 16500
}
],
"technicianId": "TECH-3f68cc26",
"estimateId": "EST-feef6ee9",
"status": "Open",
"ticket": {
"roId": "RO-1f2a3746",
"position": "Open",
"standing": "open",
"basis": "one-ticket-read-never-advanced"
}
},
"provenance": {
"simulated": true,
"environment": "sandbox",
"source": "shop-ticket-sandbox"
},
"events": [],
"meter": {
"charged": "0.00",
"posted": false
}
}Lifecycle & state
close
repairOrder.close · POST /repair-orders/close · gate key · sandbox · answers RepairOrderClose@1
No input — this capability takes no request body.
Door — aggregator.vin serves this noun on its two routes: / (the landing) · /1C4RJFBG4LC317588 (the VIN lens).
Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.
Emits — RepairOrder.closed@1.
import { repairOrder } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await repairOrder.close()curl -X POST https://apis.vin/repair-orders/close \
-H 'content-type: application/json' \
-d '{}'Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.
{
"type": "OK",
"answers": "RepairOrderClose@1",
"value": {
"vin": "1HGCM82633A004352",
"noun": "repairOrder",
"asOf": "2026-08-10",
"id": "RO-1f2a3746",
"concerns": [],
"payType": "warranty",
"lines": [
{
"line": 1,
"kind": "labor",
"description": "labor operation",
"amountCents": 16500
}
],
"technicianId": "TECH-3f68cc26",
"estimateId": "EST-feef6ee9",
"status": "Open",
"close": {
"roId": "RO-1f2a3746",
"position": "Open",
"billing": "not-yet-billed",
"standing": "not-yet-invoiced",
"basis": "ro-billing-lane-read-never-advanced"
}
},
"evidence": {
"vin": "1HGCM82633A004352",
"noun": "repairOrder",
"asOf": "2026-08-10",
"id": "RO-1f2a3746",
"concerns": [],
"payType": "warranty",
"lines": [
{
"line": 1,
"kind": "labor",
"description": "labor operation",
"amountCents": 16500
}
],
"technicianId": "TECH-3f68cc26",
"estimateId": "EST-feef6ee9",
"status": "Open",
"close": {
"roId": "RO-1f2a3746",
"position": "Open",
"billing": "not-yet-billed",
"standing": "not-yet-invoiced",
"basis": "ro-billing-lane-read-never-advanced"
}
},
"provenance": {
"simulated": true,
"environment": "sandbox",
"source": "shop-ticket-sandbox"
},
"events": [],
"meter": {
"charged": "0.00",
"posted": false
}
}More actions
start
repairOrder.start · POST /repair-orders/start · gate key · sandbox · answers RepairOrderStart@1
No input — this capability takes no request body.
Door — aggregator.vin serves this noun on its two routes: / (the landing) · /1C4RJFBG4LC317588 (the VIN lens).
Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.
Emits — RepairOrder.started@1.
import { repairOrder } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await repairOrder.start()curl -X POST https://apis.vin/repair-orders/start \
-H 'content-type: application/json' \
-d '{}'Data model
The record shape behind this noun — one entity, each property an evidence field. See the whole estate model on the data model page.
RepairOrder
Schema
| Property | Type | Notes |
|---|---|---|
id | id | ro_ |
vin | string | — |
concerns | string[] | — |
payType | enum | customer|warranty|internal |
lines | RoLine[] | — |
technicianId | ref→Provider | — |
estimateId | ref→Estimate | — |
status | RepairOrderFSM | — |
Relationships
| From | To | Cardinality | As |
|---|---|---|---|
repairOrder | estimate | 1:0..* | estimated by |
repairOrder | warrantyClaim | 1:0..* | claims |
repairOrder | appointment | 1:0..1 | scheduled |
Generated from the catalog. Every capability, answer, gate, and entity on this page is a rendered descriptor — it cannot drift from the wire.
rental
The rental noun — identity, lifecycle, events, and every capability as an anchored section: 19 capabilities, 0 live, 19 sandbox, 0 declared.
repossession
The repossession noun — identity, lifecycle, events, and every capability as an anchored section: 15 capabilities, 0 live, 15 sandbox, 0 declared.