SRDV Knowledge Centre

Why are some seat indexes missing in the Bus Seat Layout API response?

Clear, practical guidance from SRDV Technologies specialists to help you make informed travel technology decisions.

Searchable knowledge base Implementation-focused answers Guidance from travel technology experts
Expert answer

A clear answer from our specialists

Review the answer below, then contact our team if you need guidance for your own platform or integration.

SRDV expert guidanceWhy are some seat indexes missing in the Bus Seat Layout API response?

In the Bus Seat Layout API response, only the seats that are physically present in the layout are returned. Empty spaces or aisles in the bus (e.g., walking space between seats or design gaps) are not included in the Result JSON.

For example:-

  • If seat positions 1 and 2 exist, but position 3 is just an empty aisle or passage (i.e., no physical seat), then index 3 will not appear in the response.

  • The layout must be rendered dynamically by mapping the available seat positions and inserting empty spaces wherever no index exists.

Developer Note:-

You should build the seat grid based on row & column positions and fill empty gaps manually where the index is missing — these represent the physical empty spaces in the actual bus layout.

 

Sample JSON Variations:-

Array structure with row index as key:

"Result": { "0": [ { "ColumnNo": 0, ... }, { "ColumnNo": 1, ... } // No entry for Column 2 (aisle), hence it's skipped ] }

Nested object structure:

"Result": { "0": { "1": { "ColumnNo": 1, ... } // "0" is missing — indicates space } }

Need a solution-specific answer?

Plan your travel technology project with SRDV

Share your business model, supplier requirements and launch goals with our specialists.

Request a Demo Contact Us
Cloud ecosystem

Our Cloud Partners

Secure, scalable cloud infrastructure for travel technology.