Time limits
A booking carries deadlines. Each one marks a point by which you must act, and missing one releases the seats or closes a door. Read them off the booking and enforce them on your side. Never assume a deadline; use the value the API returns.
The deadlines
Reading them back
Call OTA_ReadRQ with the W1 record locator whenever you need the current values. The three fare-rule deadlines sit under fareInfos.fareInfo[].ruleInfo.tpaextensions, one block per segment, and the ticketing deadline sits with the booking’s ticketing details.
All three are in UTC. A segment that has been cancelled carries no ruleInfo at all, so expect the block to be missing for it.
Penalty windows
The same ruleInfo block carries chargesRules, the cancellation penalties broken down by time window. Each rule has an applyFromTime and an applyUntilTime in UTC, so you can tell a traveler what cancelling now would cost. See Cancelling for the fields.
The group deadline
For a group booking, add the passengers and issue the tickets no later than 72 hours before departure. This is measured from the train’s departure, not from when you made the booking. A booking made well ahead of time still has until 72 hours before the train leaves. Miss it and the booking is released. See Booking models.
If a deadline passes, the booking becomes invalid and you cannot issue its tickets. A cancel request made after that point still goes through, with the agreed cancellation and refund policy applied.

