Get Schedules Endpoint With Extra Information (DEPRECATED - V1)

⚠️ DEPRECATION NOTICE: This endpoint is deprecated and supports only Timed Schedules. Please use the new V2 endpoint which supports both Timed Schedules and Random Schedules.

Understanding Schedule Types

Before using this endpoint, it's important to understand the two types of schedules in our transport system:

Timed Schedules (Supported by This Endpoint)

Fixed departure times that work perfectly for formal transport companies operating long-distance routes. For example:

  • GUO Transport (Lagos to Abuja): 8-hour journey with strict 6 AM departure

  • Passengers must arrive on time or miss the bus

  • Creates predictability for business travelers and long-distance journeys

Random Schedules (Not Supported by This Endpoint)

Flexible timing for informal transport businesses operating shorter routes. For example:

  • Star Sunny Motors (Awka to Nnewi): 1-hour journey with flexible timing

  • Passengers can arrive throughout the day and find buses leaving soon

  • Operates with time windows rather than fixed departure times

Example of Random Schedule structure:

  • Morning Operations (5 AM - 12 PM): Shuttle buses (7 passengers) at ₦1,500 per person

  • Evening Operations (12 PM - 10 PM): Hiace buses (14 passengers) at ₦1,200 per person

Endpoint Overview

This V1 endpoint retrieves schedule information associated with a route (e.g., Lagos→Abuja) for routes using Timed Schedules only. It provides additional information compared to the original Get Schedules endpoint, including bus details, available seats, route information, terminal details, and business information.

Key Features

  • Customizable query parameters to get exactly the information needed

  • Returns schedule_id and bus seat IDs for immediate ticket purchase

  • Special note: Always pass the departure date to avoid requiring customers to change dates after purchase via email request

Limitations

  • Only works with Timed Schedules - routes with fixed departure times

  • Does not support Random Schedules with flexible timing windows

  • For Random Schedule support, migrate to the V2 endpoint

Migrating to V2

The V2 endpoint supports both Timed and Random schedules and should be used for all new integrations. The V2 endpoint provides:

  • Full support for both schedule types (Timed and Random)

  • Enhanced filtering capabilities

  • Improved response structure

  • Better performance and reliability

📘 See V2 Documentation: Link to V2 endpoint documentation

Bear in mind that if you do not pass the departure date, the user will have to change the date and select a seat through the request change they will get in their mail after the ticket purchase. So, you are advised to always pass the departure date so your user does not have to take an extra step after purchase.

Get bus schedules by route, departure and arrival city, terminal ID, business ID and departure date

get

This endpoint retrieves available bus schedules based on the provided route ID, departure and arrival city ID, terminal ID, business ID and departure date.

Query parameters
route_idintegerOptional

ID of the route to fetch schedules for.

departure_datestring · dateOptional

Departure date for which to retrieve schedules (format YYYY-MM-DD).

from_city_idintegerOptional

ID of the city where the trip originates.

Example: 12
to_city_idintegerOptional

ID of the destination city.

Example: 3
business_idstringOptional

ID of the business offering the schedule (UUID format).

Example: 6e9d9432-2a1d-4a8a-a5e4-3ddfaf832523
terminal_idintegerOptional

ID of the terminal associated with the departure.

Example: 7
Responses
chevron-right
200

List of bus schedules.

application/json
successbooleanOptionalExample: true
statusintegerOptionalExample: 200
messagestringOptionalExample: List of bus schedules
get
/api/v1/merpi/transport/schedules/packages
200

List of bus schedules.

Last updated