DS
DEVSECITEnterprise
Multi-Operator Transit Gateway

Manage transit routes with Bus Booking API

Connect your booking platforms to a global transit engine. Query schedules, render interactive seat layouts, lock seats dynamically, and issue branded electronic tickets.

Get API CredentialsExplore Endpoints

Bus API Gateway

● Online (v1.0)
TPS: 3000+

POST /api/v1/bus/seats/lock HTTP/1.1

Host: console.devsecit.com

Authorization: Bearer DSI_BUS_...

Content-Type: application/json

// Request Payload

{

"trip_id": "tp_98471abc",

"seats": ["A1", "A2"],

"hold_timeout_seconds": 600

}

10-Minute Seat Hold

PCI-DSS Compliant Checkout

1. Platform Overview & Business Architecture

The Bus Booking API is a multi-operator public transit ticketing gateway. Building ticketing applications that scale across hundreds of travel operators, route schedules, dynamic seat grids, and live inventories is a significant technical challenge. This API solves this by offering a standardized, real-time middleware layer that coordinates operator schedules, seat lay outs, ticket locking, and checkouts.

Using our API, developers can search transit schedules by origin, destination, and date; retrieve interactive, dynamic seat layouts for different bus models; lock seats temporarily to prevent duplicate bookings during checkout; and confirm bookings to issue electronic tickets.

Security is critical for transactional portals. The API utilizes cryptographically signed tokens and HTTPS/TLS 1.3 encryption to protect passenger lists, contact numbers, and billing transactions in compliance with regulatory standards.

Capabilities

2. Bus Booking Features

Dynamic Seat Mapping

Query and render interactive seat layouts for sleeper, seater, and multi-tier bus configurations.

Dynamic Seat Locking

Lock selected seats temporarily (for up to 10 minutes) during checkout to prevent duplicate bookings.

Electronic Ticket Generator

Automatically generate electronic tickets with unique QR codes for easy check-in and boarding.

Boarding Point Selectors

Query and select boarding and dropping points with accurate location data and pickup schedules.

HTTP Request (POST)Lock seats

POST https://console.devsecit.com/api/v1/bus/seats/lock

Header "Authorization: Bearer YOUR_BUS_API_KEY"

Header "Content-Type: application/json"

Request Payload (Body JSON)Body
{
  "trip_id": "tp_98471abc",
  "seats": ["A1", "A2"],
  "passenger_details": [
    { "name": "Aman", "age": 28, "gender": "M", "seat": "A1" },
    { "name": "Pooja", "age": 25, "gender": "F", "seat": "A2" }
  ],
  "hold_timeout_seconds": 600
}
Successful Response Payload200 OK
{
  "lock_id": "lk_89271ac092",
  "status": "held",
  "expires_at": "2026-08-19T06:20:00Z",
  "fare_details": {
    "base": 1200.00,
    "gst": 60.00,
    "total": 1260.00,
    "currency": "INR"
  }
}

API reference

3. API Reference & Technical Endpoints

The API operates over secure HTTPS. Below are the request and response configurations for locking seats.

    Seat maps

    4. Seat Layout Configurations

    To render seat maps correctly, our API returns detailed layout coordinates. How it works:

    • Grid Coordinates:

      Every seat contains row and column coordinates (e.g., row: 1, col: 2) to help render layout screens.

    • Seat Classifications:

      Layouts distinguish between sleeper, seater, window, and gangway seats.

    • Status Indicators:

      Seats are flagged as available, booked, locked, or reserved for female passengers.

    Security

    5. Security, High-Availability & Ticket Verification

    Operating public transit platforms requires maintaining high security and reliability standards:

    • Token & Session Security:

      Bookings are signed with client credentials, preventing unauthorized ticket modifications.

    • High-Speed Inventory Sync:

      Real-time syncing prevents double-bookings, even during peak holiday travel periods.

    • QR Ticket Validation:

      Tickets generate unique, cryptographically signed QR codes for secure boarding validation.

    • PCI-DSS Compliant Checkout:

      Payments are processed through secure, compliant gateways.

    Use cases

    6. Enterprise Use Cases

    Where teams deploy the Bus Booking API:

    • Online Travel Agencies (OTAs)

      Integrate bus ticket search, seat maps, and bookings directly into online travel portals.

    • Corporate Travel Portals

      Automate travel bookings for corporate employees, with direct booking limits and invoicing.

    • Transit Operator Software

      Provide bus operators with custom booking engines, managing schedules and inventories through our API.

    API Documentation

    Bus Booking API

    Average booking latency
    < 90ms

    Schedule queries and seat locks run over secure HTTPS.

    Gateway throughput
    3000+ TPS

    Transactions per second handled by the bus API gateway.

    Seat types supported
    Sleeper, Seater, AC, Non-AC

    Integration protocols: HTTPS / REST / JSON.

    Developer portal
    console.devsecit.com

    Sandbox rate limit for schedule queries: 60 calls/minute.

    Troubleshooting

    7. FAQ & Troubleshooting Guide

    How long can a seat lock be held?

    The default lock timeout is 10 minutes. If checkout is not completed within this time, the lock expires and seats are released.

    Does the API support ticket modifications or cancellations?

    Yes. You can cancel or modify bookings by calling the cancellation endpoint with the ticket_id, subject to the operator's policies.

    How do we fetch boarding point location maps?

    The boarding point list returned in the schedule query includes latitude and longitude coordinates for map integrations.

    What is the rate limit for schedule queries?

    Sandbox environments support up to 60 calls/minute, while production environments scale to handle high-volume searches.

    Get started

    Deploy Ticket Booking APIs

    Get your developer credentials, configure transit schedules, and integrate secure seat layout reservations today.

    Get StartedConfigure Transit Gateway