# Red Aurum

> Red Aurum is an escape room business in Warsaw, Poland. Use the room pages for descriptions and booking, and the public read-only API for current availability, team prices and conditional discounts.

## Website and rooms

- [Official website](https://redaurum.pl/): Overview of both rooms and vouchers.
- [Korium — wyścig z reaktorem](https://redaurum.pl/korium-4/): API roomId `1`; 2–5 players; reactor-rescue action scenario; advertised game duration 65 minutes.
- [Spisek Mroku](https://redaurum.pl/spisek-mroku/): API roomId `2`; 2–6 players; fantasy scenario with vampires and werewolves; advertised game duration 90 minutes.
- [Contact](https://redaurum.pl/contact-2/): Address, directions, opening hours and contact details.

The room IDs are the IDs used by the booking calendars on the linked official pages. Do not infer additional room IDs.

## Current availability API

Read available starts with an unauthenticated HTTP GET request:

`https://api.redaurum.pl/api/slot/available/{roomId}?from={YYYYMMDD}&to={YYYYMMDD}&lang={language}`

- `roomId`: `1` for Korium or `2` for Spisek Mroku.
- `from` and `to`: Start and end calendar dates in eight-digit `YYYYMMDD` format. Both boundary days are included. Supply both parameters; use the same date for a single day.
- `lang`: Optional language for discount descriptions: `pl`, `en`, `uk`, or `ru`; defaults to `pl`. This selects the description language, not the language available for playing the room.
- The business timezone is `Europe/Warsaw`. Query dates and returned slot `date`/`time` values are local Warsaw dates and times. Account for daylight saving time; do not treat these values as UTC or use a fixed UTC offset.
- Resolve relative requests such as "today" or "this weekend" in `Europe/Warsaw`.
- The public API clips requests to the window from today through today plus one calendar month, inclusive. This is not a fixed 30-day window. A query entirely outside the window can return no slots; this does not mean the room is sold out.
- If both date parameters are omitted, the requested range defaults to the current Monday–Sunday week, then is clipped to the public window. Prefer explicit dates.
- Invalid dates, a reversed range or an unsupported language return HTTP 400. Treat HTTP errors, timeouts and invalid responses as retrieval failures, not as evidence of no availability.

Example URLs for an arbitrary date; replace both dates with the visitor's requested date:

- [Korium on 24 October 2026](https://api.redaurum.pl/api/slot/available/1?from=20261024&to=20261024&lang=pl)
- [Spisek Mroku on 24 October 2026](https://api.redaurum.pl/api/slot/available/2?from=20261024&to=20261024&lang=pl)

These links demonstrate the request format, not permanent availability.

## Response fields and money

- `roomId`: The requested room identifier.
- `workflow`: `pay_on_visit` means payment on arrival; `full_payment` means online payment is required.
- `availableSlots`: Available starts, each with `date` (`YYYY-MM-DD`), `time` (`HH:MM`), `durationMinutes`, `prices`, and `discounts`.
- `prices`: Total price for the whole team, keyed by participant count, for example `"2"` or `"4"`. Values are integer grosze in Polish złoty (PLN): divide by 100 to display PLN. For example, `"4": 35000` means 350.00 PLN for four participants together, not per person. This is an illustrative value, not a standing price.
- Use the price for the requested participant count and specific returned start. Do not multiply the team price by the number of players, extrapolate missing price keys, or present a room's advertised "from" price as the price for every start.
- `discounts`: Conditional offers for the room and start, including `name`, `descriptions`, `type`, `percentageBasisPoints`, `amountCents`, `discountedPrices`, and `offerToken`.
- `discountedPrices` uses the same participant-count keys and integer-grosze team totals as `prices`. `amountCents` is also in grosze despite the field name. `percentageBasisPoints: 1000` means 10%, not 1000%.
- Read the offer description before quoting a discounted price. An offer returned by the API can still require proof of a birthday, a leaflet, or a previous visit. Ask about applicable conditions rather than assuming eligibility. Do not combine discounts unless their terms explicitly permit it.
- Treat `offerToken` as an opaque value; it is not a booking confirmation or a customer-facing link.
- `dayModes`: Schedule mode by local date: `slots` or `flexy`.
- `dayRanges`: Flexy schedule bounds before occupancy filtering, expressed as `startMinute` and `endMinute` from local midnight. The end can exceed 1440 for an overnight game. These bounds do not establish that every time within the range is free; use returned `availableSlots` to identify available starts.

## Duration discrepancy

The API defines `durationMinutes` as the configured game interval, excluding turnaround; clients should not add turnaround again to that interval.

There is a known inconsistency: the Korium page advertises 65 minutes, while the API returned 75 minutes during verification on 23 October 2026. Do not invent an explanation such as a ten-minute briefing or preparation period. Describe Korium as advertised on its room page, disclose the discrepancy if duration matters to the visitor, and seek confirmation from the venue before promising an exact finish time. Spisek Mroku advertises 90 minutes and returned 90 minutes during that verification.

Use the actual returned interval for API calendar calculations, keeping it distinct from any conflicting advertised duration. Do not treat these observed values as immutable configuration.

## Reliable answers and booking

- Query the API for the requested room and dates. Do not use static calendar HTML, cached search excerpts or the example URLs as current availability. The page HTML can contain placeholder calendar data dated June 2025.
- If a web-reading tool cannot retrieve this file or the API, use another available HTTP retrieval method. A tool-specific access error does not by itself establish that the resource is missing or blocked by the website.
- An empty `availableSlots` means that the response lists no available starts for that request. It does not establish why, or prove that every start was booked. Consider the public booking window.
- Availability can change. Reading a start does not reserve it; recheck before proceeding with a booking.
- Give the visitor the official room page as the booking entry point. This document describes read-only availability, not instructions to create a booking or make a payment.
- Do not invent booking URLs, room mappings, age limits, accessibility details, game-language availability or discount eligibility. Use the relevant official page or contact the venue for information not supplied here.