A valid request URL is required to generate request examples{
"id": "rep-2030-000471",
"article": {
"label": "Smartphone screen",
"skuId": "d4c81e5b0f7a396248ce15b7d0a83f62915ce4d7b0863af251d94c7e08b3f6a1",
"purchasedAt": "2029-01-16T09:00:00.000Z"
},
"issueDescription": "Cracked screen after a drop",
"quoteAmountCents": 12000,
"depositAmountCents": 3600,
"expectedPickupDate": "2030-07-20T18:00:00.000Z",
"customerId": "cust-1",
"storeId": "store-rivoli",
"status": "intake",
"actorId": "user-camille",
"createdAt": "2030-07-10T14:05:00.000Z",
"updatedAt": "2030-07-10T14:05:00.000Z"
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123,
"fieldErrors": [
{
"field": "<string>",
"message": "<string>"
}
]
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}Get a repair order by id
Returns ONE repair order: the article taken in, the customer’s issueDescription, the money (quoteAmountCents quoted, depositAmountCents acompte already captured at intake), the promised expectedPickupDate and the lifecycle status. updatedAt is the instant of the LAST transition and equals createdAt while the order is still at intake. The balance the customer still owes at pickup is quoteAmountCents - depositAmountCents — the API does NOT return it as a field, so compute it. Call this before any transition to confirm the current state, because none of them can be reversed. The three FORWARD verbs each advance from exactly one state (sendRepairToWorkshop from intake, markRepairReady from in_workshop, collectRepair from ready), but markRepairUnrepairable is NOT state-guarded that way: it is legal from intake, in_workshop AND ready, so a repaired order waiting at the counter can still be written off terminally in one call. Never call it speculatively expecting a 422 to protect you. 404s when no order carries the id.
A valid request URL is required to generate request examples{
"id": "rep-2030-000471",
"article": {
"label": "Smartphone screen",
"skuId": "d4c81e5b0f7a396248ce15b7d0a83f62915ce4d7b0863af251d94c7e08b3f6a1",
"purchasedAt": "2029-01-16T09:00:00.000Z"
},
"issueDescription": "Cracked screen after a drop",
"quoteAmountCents": 12000,
"depositAmountCents": 3600,
"expectedPickupDate": "2030-07-20T18:00:00.000Z",
"customerId": "cust-1",
"storeId": "store-rivoli",
"status": "intake",
"actorId": "user-camille",
"createdAt": "2030-07-10T14:05:00.000Z",
"updatedAt": "2030-07-10T14:05:00.000Z"
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123,
"fieldErrors": [
{
"field": "<string>",
"message": "<string>"
}
]
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}Authorizations
Authorization: Bearer <token>. Accepts EITHER a Keycloak access token (scopes-in-token) OR an opaque POS session token; both resolve to the same pos.* scope vocabulary the route guards enforce.
Path Parameters
1Response
The repair order in its current lifecycle state.
The repair order in its current lifecycle state.
Show child attributes
Show child attributes
-9007199254740991 <= x <= 9007199254740991-9007199254740991 <= x <= 9007199254740991intake, in_workshop, ready, collected, unrepairable