Work with ASA hotel operations

Start with a focused question

Project members use the connections enabled for their project without a separate connection grant. Viewers follow results and download shared files. Contributors ask questions and prepare changes. Managers also approve changes. Chat modes, connection approval rules and the business tool’s own access limits still apply.

Prompt	ASA methods	Access and vendor modules
“Show today’s arrivals, departures, and occupied rooms.”	getReservations, getInHouseRoomReservations	project Contributor access; ASA method permission. In-house list: Data Exchange, Cash or Charging station. Reservation queries may have limited filters without Data Exchange/Cash.
“Prepare a housekeeping handover with rooms needing attention.”	getHousekeepingStatus	project Contributor access; ASA method permission and Web Client/Housekeeping access.
“Summarize open room balances and estimated bills.”	getOpenPasserByAccounts, getCurrentRoomAccountBalance, getEstimatedRoomBill	project Contributor access; ASA method permission. Open accounts: Data Exchange or Cash; room balances/estimated bills: Pay-TV Guest-Info.
“Review dining assignments and propose these table changes.”	getInHouseRoomReservations, updateDiningInfo	Contributor access; Cash for updates; approve the proposal in Ask for approval mode.
“Find spa appointments and prepare an approved booking or status change.”	getSpaAppointments, getAvailableSpaSlots, postSpaAppointment, setSpaAppointmentStatus	Contributor access and a project Manager for approval; ASA method permission. Booking needs Ext. Reservation-Service; Beauty additionally requires Data Exchange. Ask the administrator about the applicable method-specific modules.
“Prepare these minibar charges for review.”	postRoomCharge plus an occupant read if targeting a room number	Contributor access and a project Manager for approval; ASA method permission and Cash, Pay-TV Guest-Info, Room systems or Charging station.

Treat module requirements as vendor prerequisites, not grants inferred from a connection test. Steward supports all 33 methods in the v2.14 Reservation Service contract. Unknown methods and fields are blocked.

You need Manager access to the proposal’s project to approve or reject changes. Contributors can prepare changes and review the details. Approval rechecks the executor’s current project access and the enabled connection before execution.

Give the assistant clear targets

For charges, provide the ASA article code, quantity and decimal amount, plus a stable account, room-reservation or room-guest identifier. A global guest ID differs from a room-guest ID; a hotel reservation ID differs from its room-reservation ID. Ask the assistant to retrieve and confirm the correct identity before preparing a change.

If only a room number is supplied, Steward binds the proposal to the current reservation and room-guest identities and checks again before execution. A guest change within the same reservation also stops the proposal. Prepare a fresh proposal after a change. Keep separate charge documents for separate occupied rooms.

For dining changes, provide the occupied room and table, diningRoomAnnotation or kitchenAnnotation. Omitted fields preserve existing values; explicit empty text clears them. diningAnnotation is computed in the demonstrated deployment and is not writable through this adapter.

For housekeeping, identify a room, house, group or floor and the intended change. Status fields are siblings of the room element, not nested inside it.

Review the proposal

Check the operation, target identities, amounts, dates and changed fields. Consequential changes require review by default. Approval applies to the prepared request. A changed destination, credential revision, contract or applicable rule requires a fresh proposal.

If an execution times out or returns unreadable XML, the result may be uncertain. Consult ASA and the recorded execution result before requesting another attempt. Completed batch items remain completed; later items may stop after cancellation, revocation or changed conditions.

Understand the data limits

Guest searches use exact criteria; do not expect a wildcard search or unrestricted guest directory. Empty results are valid. Optional values can be absent, multilingual labels can repeat, and monetary values remain exact decimal strings.

Only fields in Steward’s reviewed ASA contract are returned. Newly added vendor fields become available after contract review. Charging start/stop accepts room, room-reservation, room-guest, key or vehicle selectors; ASA does not support accountID for those controls.

Use hotel-local dates. Billing data can disappear when an account closes, so an estimated bill read later may differ from a previously captured result. ASA errors returned inside HTTP 200 are still failures.

Example SOAP read

The assistant can retrieve one operation contract with describe_integrations and its operation-name filter. Generated code uses the existing Steward HTTPX client. Credentials, service destination, SOAPAction and API version are supplied by the backend.

import steward_http

xml = b'''<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
  <env:Body><getReservations xmlns="http://www.asahotel.com/hotel">
    <arrival><fromDate>2026-10-04</fromDate><toDate>2026-10-04</toDate></arrival>
  </getReservations></env:Body>
</env:Envelope>'''
async with steward_http.AsyncClient(connection=connection_id) as client:
    response = await client.post("/", content=xml, headers={"Content-Type": "text/xml"})
    response.raise_for_status()

Steward uses the project role and chat mode to authorize ASA work. ASA separately checks the saved account’s method permissions and licensed modules. SOAP reads work in Read only mode even though they use POST. The observed-access panel is advisory and never grants access.