SRDV Knowledge Centre

The API response shows two keys: Result and ResultUpperSeat. Why are both included?

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 guidanceThe 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:-

  1. Use both keys to render a complete layout.

  2. Handle the case where only one of them is populated (e.g., if the bus has only lower deck seats).

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.