Room service
Send a checked-in room’s order to Rasnos and charge the folio.
Room service is the link between Agamnos and Rasnos. Front desk picks a checked-in stay, opens a menu category, orders from the Rasnos menu, and the kitchen ticket is created in Rasnos.
Charge to room posts a food line on that stay’s folio as soon as Rasnos accepts the order. The folio and Generate invoice show the date and time that charge was posted. Complimentary orders skip the folio.
If two stays are still checked into the same room, pick the guest by name. A stay past checkout is not the default.
The folio URL and shared key live in Rasnos staff settings. Platform env on Agamnos must point at Rasnos; the folio charge key must match what Rasnos sends.
Technical
- Staff console (JWT + front-desk permission): GET /api/v1/room-service/status, GET /api/v1/room-service/menu?propertyId=, GET /api/v1/room-service/in-house?propertyId=, POST /api/v1/room-service/orders.
- Rasnos → Agamnos folio post (no JWT): POST /api/v1/folio/charge with header x-api-key matching RASNOS_FOLIO_API_KEY.
- Agamnos → Rasnos: RASNOS_API_URL (base), RASNOS_API_KEY (staff/API key), optional RASNOS_TENANT_HOST / property code mapping for the hotel kitchen.
- Status on Room service reports whether URL, API key, and folio key are configured—not guest PII.