You can get quick answer of your question by entering here
The API response shows two keys: Result and ResultUpperSeat. Why are both included?
The API response includes two separate keys to handle buses with dual-level seating layouts:
-
Result: Represents the lower deck seat layout. -
ResultUpperSeat: Represents the upper deck seat layout.
This structure has always been part of the API to clearly differentiate between lower and upper sleeper seats — especially useful for sleeper or multi-level buses.
Your integration should:
-
Use both keys to render a complete layout.
-
Handle the case where only one of them is populated (e.g., if the bus has only lower deck seats).