A valid request URL is required to generate request examples{
"id": "appt-ok",
"associateId": "user-julie",
"customerId": "cust-1",
"storeId": "store-rivoli",
"startsAt": "2030-01-01T10:00:00.000Z",
"endsAt": "2030-01-01T11:00:00.000Z",
"status": "requested",
"actorId": "user-julie",
"bookedAt": "2026-07-28T09:00: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
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}Book an appointment (RDV)
Books a customer (rendez-vous) with a sales associate for a half-open [startsAt, endsAt) slot (ISO 8601 instants the server coerces), creating it requested. The CALLER supplies the appointment id — it must be unique, so choose a stable, collision-free identifier (a duplicate is rejected with a 409, never silently merged). The slot must be forward-ordered and in the future. 409s when the slot overlaps another active booking for the same associate, or when the id already exists; 422s for a slot already in the past.
A valid request URL is required to generate request examples{
"id": "appt-ok",
"associateId": "user-julie",
"customerId": "cust-1",
"storeId": "store-rivoli",
"startsAt": "2030-01-01T10:00:00.000Z",
"endsAt": "2030-01-01T11:00:00.000Z",
"status": "requested",
"actorId": "user-julie",
"bookedAt": "2026-07-28T09:00: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
}
}{
"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.
Body
Caller-supplied unique appointment (RDV) id; a duplicate 409s.
1Sales associate the customer is booked with.
1Customer the rendez-vous is for.
1Store the appointment takes place in.
1ISO 8601 inclusive slot start; must be in the future.
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$ISO 8601 exclusive slot end; must be after startsAt.
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$Response
The booked appointment in its requested state.
The booked appointment in its requested state.

