I'm building an SYOS application for a venue that has seats physically close together but technically in different zones (tables, booths, barstools). I can imagine a scenario where a user would choose seats from a few different zones all at once. According to the API documentation, ReserveTicketsSpecifiedSeats() requires a single zone ID, which would seem to exclude reserving seats from multiple zones in the same request. This would be a pretty big inconvenience, so I've been experimenting with the ReserveTicketsSpecifiedSeats() method. I found that although it isn't mentioned in the documentation, the iZone and iNumberOfSeats parameters can be set to zero, at least when the RequestedSeats parameter is supplied. Seats reserved in this manner appear as subline items in the cart as expected, and under a single line item, although that line item only has a single zone ID property which only applies to some of its subline items.
This seems workable to me, but does anyone know of any caveats of using ReserveTicketsSpecifiedSeats() in this manner?
On a side note, why would ReserveTicketsSpecifiedSeats() require a zone ID and number of seats at all, but not require the requested seat IDs? Isn't that the point of the method, to reserve specific seats as opposed to the automatic selection performed by ReserveTicketsEx()?
Thanks for your input!Bryan