Reservation Services Back-End Agent
Builds the reservation, rate and availability services behind the booking channels.
- Industry
- Hotel
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- Head of Hotel Technology
- Code
- ENG-02
It implements the services behind direct booking and the group's own tools (availability and rate lookups, reservation create, modify and cancel, deposit and cancellation rules, loyalty point accrual) against the central reservation system and the property management system, keeping the published API contract backward compatible. It opens a pull request with unit and contract tests and the updated API specification, and flags anything that changes a booking contract, stored guest data, authentication or how a card token is handled.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the code repository: the reservation services code, the published API specification and the contract tests for the endpoints named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Head of Hotel Technology with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the code repository: it opens a pull request with the change, tests and updated API specification. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The reservation services design: the booking API contract, the rate and availability model (rate plans, length-of-stay restrictions, closed-to-arrival), the cancellation and deposit rules, the PCI DSS tokenisation rules and the guest data retention policy.
Reads from
the code repository: the reservation services code, the published API specification and the contract tests for the endpoints named.
Acts in
the code repository: it opens a pull request with the change, tests and updated API specification.
Hands back
An object with pull_request_title, endpoints (a list, each with name, change and breaking true or false), flows_touched (a list), tests_added (a list), coverage_percent, guest_data_impact (text or null) and consumer_notices (a list, each with consumer and message).
Asks a person when
The change breaks a booking contract, alters stored guest data or card token handling, changes authentication, or changes how cancellation or deposit rules are applied.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| When a booking contract would break | new_version_required | What happens when a change would break callers of the reservation API. |
| Availability lookup budget at p95 (ms) | 400 | An availability or rate lookup slower than this at p95 loses bookings and is not ready. |
| Test coverage for changed code (%) | 80 | Changed reservation logic below this coverage is flagged. |
| Notice before an old API version is retired (days) | 90 | How long callers are warned before an old endpoint stops. |
| Require an idempotency key on booking writes | On | When on, create, modify and cancel calls must be safe to retry so a timeout never makes a double booking. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Keep the reservation API backward compatible; a breaking change follows new_version_required, with 90 days' notice to every consumer named.
- When on is true, every create, modify and cancel takes an idempotency key so a retried call never makes a duplicate reservation or charges a deposit twice.
- Apply the rate plan's cancellation, deposit and length-of-stay rules from the central reservation system; never hard-code a policy in the service.
- Store only card tokens from the payment provider, never card numbers or security codes, and keep guest data within the retention policy.
- Keep availability and quote lookups within 400 ms at p95 and cover changed logic to 80 percent.
- Flag any change to authentication, stored guest data or card handling for the Head of Hotel Technology.
See the Reservation Services Back-End Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.