Page Introduction

Page contract details

This contract page maps concrete frontend page behavior to API calls, payloads, and response fields.

Use the endpoint matrix as implementation checklist.
Use page-specific try-it for fast request verification.
Keep request/response shape aligned with listed frontend usage fields.

Choose next step

Back to soft-launch collection Open collection try-it Open workshop onboarding

Platform Page Contract

04 - Bookings

## Page purpose Bestillingsområdet (`/booking` + `/booking/[id]`) dekker liste, filtrering, walk-in opprettelse, statusstyring og meldingsdialog.

12Mapped endpoints

4Frontend files

35Lines

2.7 KBFile size

Source: API-DOC/page-api-mapping/04-bestillinger.md

Back to Platform Collection Open page-specific Try-It Collection Try-It

Mapped endpoints for this page

GET /api/ws/v2/bookings GET /api/ws/bookings GET /api/ws/v2/booking-statuses GET /api/ws/booking-statuses GET /api/ws/v2/bookings/:id GET /api/ws/v2/bookings/:id/valid-transitions POST /api/ws/v2/bookings/status-transitions POST /api/ws/v2/bookings/:id/messages POST /api/ws/bookings/status POST /api/ws/bookings/message/:booking_id POST /api/ws/bookings GET /api/ws/services

Method	Path	Scope	UI usage	Test
GET	`/api/ws/v2/bookings`	Shared	Fetch bookingliste	Try-It
GET	`/api/ws/bookings`	Shared fallback (feature-flagged)	Legacy fallback ved migrering	Try-It
GET	`/api/ws/v2/booking-statuses`	Shared	Statusfilter/statusvalg	Try-It
GET	`/api/ws/booking-statuses`	Shared fallback (feature-flagged)	Legacy fallback	Try-It
GET	`/api/ws/v2/bookings/:id`	Page-specific	Bookingdetalj	Try-It
GET	`/api/ws/v2/bookings/:id/valid-transitions`	Page-specific	Tillatte overganger	Try-It
POST	`/api/ws/v2/bookings/status-transitions`	Page-specific (kanonisk write)	Bekreft/avbestill/fullfør/reschedule	Try-It
POST	`/api/ws/v2/bookings/:id/messages`	Page-specific (kanonisk write)	Send melding i bookingtråd	Try-It
POST	`/api/ws/bookings/status`	Page-specific fallback (flaggstyrt)	Legacy fallback for status	Try-It
POST	`/api/ws/bookings/message/:booking_id`	Page-specific fallback (flaggstyrt)	Legacy fallback for melding	Try-It
POST	`/api/ws/bookings`	Page-specific	Create walk-in booking	Try-It
GET	`/api/ws/services`	Shared	Services til walk-in dropdown	Try-It

GET/api/ws/v2/bookings

Scope: Shared

UI usage: Fetch bookingliste

Response fields used: items[] med booking-kjernefelt

GET/api/ws/bookings

Scope: Shared fallback (feature-flagged)

UI usage: Legacy fallback ved migrering

Response fields used: legacy booking list

GET/api/ws/v2/booking-statuses

Scope: Shared

UI usage: Statusfilter/statusvalg

Response fields used: statuses[].code, label, allowed_transitions, color, icon

GET/api/ws/booking-statuses

Scope: Shared fallback (feature-flagged)

UI usage: Legacy fallback

Response fields used: legacy statusobjekter

GET/api/ws/v2/bookings/:id

Scope: Page-specific

UI usage: Bookingdetalj

Response fields used: booking, messages, timeline, group

GET/api/ws/v2/bookings/:id/valid-transitions

Scope: Page-specific

UI usage: Tillatte overganger

Response fields used: current_status, allowed_transitions[]

POST/api/ws/v2/bookings/status-transitions

Scope: Page-specific (kanonisk write)

UI usage: Bekreft/avbestill/fullfør/reschedule

Response fields used: updated[], failed[], totals

POST/api/ws/v2/bookings/:id/messages

Scope: Page-specific (kanonisk write)

UI usage: Send melding i bookingtråd

Response fields used: booking_id, message

POST/api/ws/bookings/status

Scope: Page-specific fallback (flaggstyrt)

UI usage: Legacy fallback for status

Response fields used: oppdateringsresultat

POST/api/ws/bookings/message/:booking_id

Scope: Page-specific fallback (flaggstyrt)

UI usage: Legacy fallback for melding

Response fields used: melding/OK

POST/api/ws/bookings

Scope: Page-specific

UI usage: Create walk-in booking

Response fields used: opprettet booking

GET/api/ws/services

Scope: Shared

UI usage: Services til walk-in dropdown

Response fields used: items[] med id, title, price

Try this page endpoints

Interactive console below is filtered to endpoints mapped for this page contract.

Source markdown

04 - Bookings

Page purpose

Bestillingsområdet (/booking + /booking/[id]) dekker liste, filtrering, walk-in opprettelse, statusstyring og meldingsdialog.

Frontend methods and components

List:
- src/features/bookings/BookingTable.tsx
- src/lib/hooks/useBookings.ts
Detalj:
- src/features/bookings/BookingDetails.tsx
Walk-in:
- src/features/bookings/CreateWalkInBookingModal.tsx

Endpoint matrix (liste + detalj)

Scope	Method	Endpoint	UI usage	Request	Response fields used by frontend
Shared	`GET`	`/api/ws/v2/bookings`	Fetch bookingliste	`limit`, `cursor`, `status`, `from`, `to`, `q`, `sort`, `format`	`items[]` med booking-kjernefelt
Shared fallback (feature-flagged)	`GET`	`/api/ws/bookings`	Legacy fallback ved migrering	legacy query params	legacy booking list
Shared	`GET`	`/api/ws/v2/booking-statuses`	Statusfilter/statusvalg	ingen	`statuses[].code`, `label`, `allowed_transitions`, `color`, `icon`
Shared fallback (feature-flagged)	`GET`	`/api/ws/booking-statuses`	Legacy fallback	ingen	legacy statusobjekter
Page-specific	`GET`	`/api/ws/v2/bookings/{id}`	Bookingdetalj	`include=services,messages,timeline,group`	`booking`, `messages`, `timeline`, `group`
Page-specific	`GET`	`/api/ws/v2/bookings/{id}/valid-transitions`	Tillatte overganger	path `id`	`current_status`, `allowed_transitions[]`
Page-specific (kanonisk write)	`POST`	`/api/ws/v2/bookings/status-transitions`	Bekreft/avbestill/fullfør/reschedule	`booking_ids`, `target_status`, `apply_scope`, `reason`, `scheduled_at`, `metadata`	`updated[]`, `failed[]`, `totals`
Page-specific (kanonisk write)	`POST`	`/api/ws/v2/bookings/{id}/messages`	Send melding i bookingtråd	`{ content/message, attachments, to_carowner }`	`booking_id`, `message`
Page-specific fallback (flaggstyrt)	`POST`	`/api/ws/bookings/status`	Legacy fallback for status	legacy body	oppdateringsresultat
Page-specific fallback (flaggstyrt)	`POST`	`/api/ws/bookings/message/{booking_id}`	Legacy fallback for melding	`{ message, to_carowner, attachments }`	melding/OK
Page-specific	`POST`	`/api/ws/bookings`	Create walk-in booking	`service_id`, `start_at`, `walk_in`, kunde-/kjøretøyfelt, `notes`	opprettet booking
Shared	`GET`	`/api/ws/services`	Services til walk-in dropdown	`page_size=200`, `sort=title`	`items[]` med `id`, `title`, `price`

Contract summary

Lesekontrakt er v2-first (/v2/bookings*).
Skrivekontrakt er v2-first (/v2/bookings/status-transitions + /v2/bookings/{id}/messages).
Legacy booking write-ruter er fortsatt tilgjengelige, men deprecated og brukes kun via flaggstyrt fallback.