### Response example for GET /v1/lookup/stations/ntes

Source: https://railradar.in/docs/ntes-stations-lookup

Example JSON response with a success flag, data mapping station codes to names, and metadata including traceId, timestamp, executionTime, and source.

```json
{
  "success": true,
  "data": {
    "NDLS": "NEW DELHI",
    "AGC": "AGRA CANTT",
    "INDB": "INDORE JN",
    "MMCT": "MUMBAI CENTRAL"
  },
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### JSON response example for GET /v1/legacy/trains/all-kvs

Source: https://railradar.in/docs/legacy-all-trains-kvs

Example 200 OK response showing the success flag, data array of [Number, Name] pairs, and meta information including traceId, timestamp, executionTime, and source.

```json
{
  "success": true,
  "data": [
    [
      "12919",
      "Malwa Express"
    ],
    [
      "12920",
      "Malwa Express (Return)"
    ],
    [
      "12002",
      "New Delhi - Bhopal Shatabdi Express"
    ]
  ],
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### Successful response example (200 OK)

Source: https://railradar.in/docs/local-train-cities

Example JSON response returned on success, containing a list of cities with train counts and metadata.

```json
{
  "success": true,
  "data": [
    {
      "city": "Mumbai",
      "count": 1850
    },
    {
      "city": "Kolkata",
      "count": 1420
    },
    {
      "city": "Chennai",
      "count": 890
    },
    {
      "city": "Hyderabad",
      "count": 320
    }
  ],
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### Response example for GET /v1/lookup/trains

Source: https://railradar.in/docs/train-lookup

Example 200 OK response showing a successful lookup with a data map of train numbers to names and metadata including traceId, timestamp, executionTime, and source.

```json
{
  "success": true,
  "data": {
    "12002": "New Delhi - Bhopal Shatabdi Express",
    "12919": "Malwa Express",
    "12920": "Malwa Express (Return)"
  },
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### Successful response example (200 OK)

Source: https://railradar.in/docs/legacy-live-map

Example JSON response from the live map endpoint showing train positions, including train number, name, type, current and next station details, and metadata.

```json
{
  "success": true,
  "data": [
    {
      "train_number": "00111",
      "train_name": "BIRD-SGTY RAPID CARGO",
      "type": "PEXP",
      "mins_since_dep": 1271,
      "current_station": "PJB",
      "current_station_name": "Paniajob",
      "current_lat": 21.18384,
      "current_lng": 80.69371,
      "departure_minutes": 1180,
      "current_day": 2,
      "next_station": "DGG",
      "next_station_name": "Dongargarh",
      "next_lat": 21.18542,
      "next_lng": 80.76165,
      "next_arrival_minutes": 1190,
      "curr_distance": 990.8,
      "next_distance": 998.7
    },
    {
      "train_number": "00132",
      "train_name": "DMO MMTDY BHGV SPL",
      "type": "Mail/Express",
      "mins_since_dep": 71,
      "current_station": "MNWL",
      "current_station_name": "Manwal",
      "current_lat": 32.76921,
      "current_lng": 75.13197,
      "departure_minutes": 1177,
      "current_day": 1,
      "next_station": "SGRR",
      "next_station_name": "Sangar",
      "next_lat": 32.80444,
      "next_lng": 75.04976,
      "next_arrival_minutes": 1191,
      "curr_distance": 46.2,
      "next_distance": 56.1
    }
  ],
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### JSON response example for live station board

Source: https://railradar.in/docs/station-live-board

Example 200 OK response for the live station board endpoint. Shows the station info, time window, train list with live status, and metadata.

```json
{
  "success": true,
  "data": {
    "station": {
      "code": "INDB",
      "name": "Indore Junction"
    },
    "window": {
      "from": "07:54",
      "to": "15:54",
      "hoursBack": 4,
      "hoursAhead": 4
    },
    "count": 1,
    "trains": [
      {
        "train": {
          "number": "12919",
          "name": "Malwa SF Express",
          "type": "Superfast Express",
          "source": "INDB",
          "destination": "SVDK",
          "runDays": [
            "mon",
            "tue",
            "wed",
            "thu",
            "fri",
            "sat",
            "sun"
          ]
        },
        "stop": {
          "sequence": 1,
          "arrival": null,
          "departure": "23:55",
          "day": 1,
          "distance": 0
        },
        "live": {
          "type": "at-station",
          "expectedDepartureTime": "2026-06-22T23:55:00+05:30",
          "platform": "4",
          "delayMinutes": 0
        }
      }
    ]
  },
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### Python requests example for train details

Source: https://railradar.in/docs/get-train-details

Python example using requests to call the train details endpoint. Not shown in the source, but the tab label indicates a Python example.

```python
# Python example not provided in source
```

--------------------------------

### JavaScript fetch example for train details

Source: https://railradar.in/docs/get-train-details

JavaScript example using fetch to call the train details endpoint. Not shown in the source, but the tab label indicates a JavaScript example.

```javascript
// JavaScript example not provided in source
```

--------------------------------

### Response example for compressed PRS trains

Source: https://railradar.in/docs/compressed-prs-trains-lookup

Example JSON response with success flag, data string, and metadata.

```json
{
  "success": true,
  "data": "12919|MALWA EXPRESS|DADN|SVDK\n12952|MUMBAI RAJDHANI|NDLS|MMCT\n12002|BHOPAL SHATABDI|NDLS|RKMP",
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### Standard Response Envelope Example

Source: https://railradar.in/docs

Example of a successful response wrapped in the standard envelope. Shows the structure with success, data, and meta fields.

```json
{
  "success": true,
  "data": {
    "trainNumber": "12952",
    "trainName": "MUMBAI RAJDHANI",
    "status": "running",
    "delayMinutes": 12
  },
  "meta": {
    "traceId": "c4b44917-8e67-4279-b1ff-97f22a5ec2ec",
    "timestamp": "2026-08-16T19:00:00+05:30",
    "executionTime": 24,
    "source": "database"
  }
}
```

--------------------------------

### Successful response example (200 OK)

Source: https://railradar.in/docs/ntes-trains-lookup

Example JSON response returned by the endpoint on success. Contains a data object mapping train numbers to train names and a meta object with traceId, timestamp, executionTime, and source.

```json
{
  "success": true,
  "data": {
    "12002": "BHOPAL SHATABDI",
    "12919": "MALWA EXPRESS",
    "12952": "MUMBAI RAJDHANI"
  },
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### 404 Not Found error response example

Source: https://railradar.in/docs/legacy-all-trains-kvs

Example error envelope for a 404 Not Found response, showing the error code NOT_FOUND and a message with an example train and date.

```json
{
  "success": false,
  "error": {
    "code": "NOT_FOUND",
    "message": "Resource not found (e.g. Train 12919 not found on journey date 2026-06-22)"
  },
  "meta": {
    "traceId": "9772f1c9-6ec6-4d9f-b269-a5210f33ec73",
    "timestamp": "2026-06-22T08:14:00+05:30",
    "executionTime": 5,
    "source": "database"
  }
}
```

--------------------------------

### Example 200 OK response for Train Details API (Legacy)

Source: https://railradar.in/docs/legacy-get-train-details

Example 200 OK response for a successful request to the legacy Train Details endpoint. Shows train info, route with delays, live data, and metadata.

```json
{
  "success": true,
  "data": {
    "train": {
      "number": "12919",
      "name": "Malwa SF Express",
      "type": "Superfast Express",
      "runDays": [
        "mon",
        "tue",
        "wed",
        "thu",
        "fri",
        "sat",
        "sun"
      ],
      "sourceCode": "INDB",
      "destinationCode": "SVDK"
    },
    "route": [
      {
        "stationCode": "INDB",
        "stationName": "Indore Junction",
        "sequence": 1,
        "scheduledArrival": null,
        "scheduledDeparture": "23:55",
        "actualArrival": null,
        "actualDeparture": "23:55",
        "delayMinutes": 0,
        "isHalt": true,
        "platform": "4"
      },
      {
        "stationCode": "UJN",
        "stationName": "Ujjain Junction",
        "sequence": 2,
        "scheduledArrival": "00:55",
        "scheduledDeparture": "01:00",
        "actualArrival": "01:07",
        "actualDeparture": "01:12",
        "delayMinutes": 12,
        "isHalt": true,
        "platform": "1"
      }
    ],
    "liveData": {
      "trainNumber": "12919",
      "journeyDate": "2026-03-14",
      "lastUpdatedAt": "2026-03-14T11:42:00+05:30",
      "currentLocation": {
        "stationCode": "UJN",
        "status": "departed",
        "segmentProgress": 0.45
      },
      "overallDelayMinutes": 12,
      "dataSource": "external",
      "route": [],
      "exceptionInfo": null
    },
    "metadata": {
      "generatedAt": "2026-06-22T12:30:00+05:30",
      "lastLiveUpdate": "2026-03-14T11:42:00+05:30"
    }
  },
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### Successful response example for Journey Overlay API

Source: https://railradar.in/docs/journey-overlay

Example JSON response for a successful request, containing delay and reliability data for the requested train-station pairs.

```json
{
  "success": true,
  "data": {
    "delays": [
      {
        "train": "12002",
        "station": "BPL",
        "dayOfWeek": 1,
        "arrivalDelayMinutes": 8,
        "departureDelayMinutes": 0,
        "samples": 28,
        "maxDelayMinutes": 45,
        "ontimeCount": 24
      },
      {
        "train": "12954",
        "station": "MMCT",
        "dayOfWeek": 3,
        "arrivalDelayMinutes": 4,
        "departureDelayMinutes": 0,
        "samples": 30,
        "maxDelayMinutes": 18,
        "ontimeCount": 27
      }
    ],
    "reliability": [
      {
        "train": "12002",
        "cancelRate": 0.01,
        "divertRate": 0,
        "samples": 90
      },
      {
        "train": "12954",
        "cancelRate": 0,
        "divertRate": 0,
        "samples": 90
      }
    ],
    "exceptions": [],
    "delaysAvailable": true,
    "liveAvailable": true
  },
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### JSON response example for train 12919

Source: https://railradar.in/docs/get-train-details

Example 200 OK response for the train details endpoint, showing train metadata and route halts.

```json
{
  "success": true,
  "data": {
    "train": {
      "number": "12919",
      "name": "Malwa SF Express",
      "type": "Superfast Express",
      "category": "Superfast",
      "source": {
        "code": "INDB",
        "name": "Indore Junction"
      },
      "destination": {
        "code": "SVDK",
        "name": "Shri Mata Vaishno Devi Katra"
      },
      "runDays": [
        "mon",
        "tue",
        "wed",
        "thu",
        "fri",
        "sat",
        "sun"
      ],
      "distance": 1640,
      "duration": 1720,
      "avgSpeed": 57.2,
      "maxSpeed": 110,
      "totalHalts": 45,
      "returnTrain": "12920",
      "coachPosition": "Engine-H1-A1-A2-B1-B2-B3-B4-PC-S1-S2-S3-S4-S5-S6-S7-S8-S9-S10-S11-S12-DL1"
    },
    "route": [
      {
        "sequence": 1,
        "station": {
          "code": "INDB",
          "name": "Indore Junction"
        },
        "arrival": null,
        "departure": "23:55",
        "arrivalDay": 1,
        "departureDay": 1,
        "distance": 0,
        "isHalt": true,
        "platform": "4",
        "speedToNextStationKmph": 55
      },
      {
        "sequence": 2,
        "station": {
          "code": "UJN",
          "name": "Ujjain Junction"
        },
        "arrival": "00:55",
        "departure": "01:00",
        "arrivalDay": 2,
        "departureDay": 2,
        "distance": 55,
        "isHalt": true,
        "platform": "1",
        "speedToNextStationKmph": 60
      }
    ]
  },
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### 200 OK response example for station timetable board

Source: https://railradar.in/docs/station-board

Example 200 OK response for the station timetable board endpoint. Shows the station info, train details, and stop information for a single train. The meta object includes traceId, timestamp, executionTime, and source.

```json
{
  "success": true,
  "data": {
    "station": {
      "code": "INDB",
      "name": "Indore Junction"
    },
    "count": 1,
    "includeIntermediate": false,
    "trains": [
      {
        "train": {
          "number": "12919",
          "name": "Malwa SF Express",
          "type": "Superfast Express",
          "source": {
            "code": "INDB",
            "name": "Indore Junction"
          },
          "destination": {
            "code": "SVDK",
            "name": "Shri Mata Vaishno Devi Katra"
          },
          "runDays": [
            "mon",
            "tue",
            "wed",
            "thu",
            "fri",
            "sat",
            "sun"
          ]
        },
        "stop": {
          "sequence": 1,
          "arrival": null,
          "departure": "23:55",
          "arrivalDay": 1,
          "departureDay": 1,
          "distance": 0,
          "stopType": "origin"
        }
      }
    ]
  },
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### Successful response example

Source: https://railradar.in/docs/filter-trains

Example 200 OK response from the Filter Trains API. Shows a list of matching trains with train number, name, category, and type, along with metadata including traceId, timestamp, executionTime, and source.

```json
{
  "success": true,
  "data": [
    {
      "train_number": "12919",
      "train_name": "Malwa SF Express",
      "category": "Superfast",
      "type": "SF"
    },
    {
      "train_number": "12952",
      "train_name": "Mumbai Rajdhani Express",
      "category": "Premium",
      "type": "RAJ"
    },
    {
      "train_number": "22436",
      "train_name": "Vande Bharat Express",
      "category": "Premium",
      "type": "VB"
    }
  ],
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### JSON Response Example for Train Coach API

Source: https://railradar.in/docs/train-coaches

Example 200 OK response for the coach API. Contains train details, coach list with positions, class blueprints (e.g., 3A with berth types), summary counts, reversal stations, stops, and legs. The source shows a partial response with only a subset of coaches for brevity.

```json
{
  "success": true,
  "data": {
    "trainNumber": "12952",
    "trainName": "Mumbai Rajdhani Express",
    "baseFormation": "ENG-EOG-H1-A1-A2-A3-A4-A5-B1-B2-B3-B4-B5-B6-B7-B8-B9-B10-B11-PC-EOG",
    "totalCoaches": 21,
    "coaches": [
      {
        "position": 1,
        "code": "ENG",
        "category": "ENG",
        "classType": "ENG",
        "name": "Locomotive",
        "totalBerths": 0,
        "hasSeats": false,
        "color": "#64748b"
      },
      {
        "position": 2,
        "code": "EOG",
        "category": "EOG",
        "classType": "EOG",
        "name": "End on Generator",
        "totalBerths": 0,
        "hasSeats": false,
        "color": "#64748b"
      },
      {
        "position": 3,
        "code": "H1",
        "category": "1A",
        "classType": "1A",
        "name": "AC First Class (H1)",
        "totalBerths": 24,
        "hasSeats": true,
        "color": "#dc2626"
      },
      {
        "position": 4,
        "code": "A1",
        "category": "2A",
        "classType": "2A",
        "name": "AC 2 Tier (A1)",
        "totalBerths": 48,
        "hasSeats": true,
        "color": "#2563eb"
      },
      {
        "position": 9,
        "code": "B1",
        "category": "3A",
        "classType": "3A",
        "name": "AC 3 Tier (B1)",
        "totalBerths": 72,
        "hasSeats": true,
        "color": "#0284c7"
      },
      {
        "position": 20,
        "code": "PC",
        "category": "PC",
        "classType": "PC",
        "name": "Pantry Car",
        "totalBerths": 0,
        "hasSeats": false,
        "color": "#f59e0b"
      },
      {
        "position": 21,
        "code": "EOG",
        "category": "EOG",
        "classType": "EOG",
        "name": "End on Generator",
        "totalBerths": 0,
        "hasSeats": false,
        "color": "#64748b"
      }
    ],
    "blueprints": {
      "3A": {
        "classCode": "3A",
        "className": "AC 3 Tier",
        "totalBerths": 72,
        "hasSeats": true,
        "cabins": [
          {
            "cabinNumber": 1,
            "main": [
              {
                "number": 1,
                "type": "LB",
                "name": "Lower Berth"
              },
              {
                "number": 2,
                "type": "MB",
                "name": "Middle Berth"
              },
              {
                "number": 3,
                "type": "UB",
                "name": "Upper Berth"
              }
            ],
            "side": [
              {
                "number": 7,
                "type": "SL",
                "name": "Side Lower"
              },
              {
                "number": 8,
                "type": "SU",
                "name": "Side Upper"
              }
            ]
          }
        ]
      }
    },
    "summary": {
      "3A": 11,
      "2A": 5,
      "1A": 1,
      "PC": 1,
      "EOG": 2,
      "ENG": 1
    },
    "reversals": [
      "BRC"
    ],
    "stops": {},
    "legs": []
  },
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### 200 OK response example for Platform Coach Position API

Source: https://railradar.in/docs/station-coach-position

Example 200 OK response for the Platform Coach Position API. Shows the train number, station code, direction, platform, formation string, and an array of coach objects with position, code, category, class type, name, berth count, seat availability, and color.

```json
{
  "success": true,
  "data": {
    "trainNumber": "12952",
    "stationCode": "BRC",
    "stationName": "Vadodara Junction",
    "direction": "UP",
    "platform": "2",
    "formation": "ENG-EOG-H1-A1-A2-A3-A4-A5-B1-B2-B3-B4-B5-B6-B7-B8-B9-B10-B11-PC-EOG",
    "coaches": [
      {
        "position": 1,
        "code": "ENG",
        "category": "ENG",
        "classType": "ENG",
        "name": "Locomotive",
        "totalBerths": 0,
        "hasSeats": false,
        "color": "#64748b"
      },
      {
        "position": 3,
        "code": "H1",
        "category": "1A",
        "classType": "1A",
        "name": "AC First Class (H1)",
        "totalBerths": 24,
        "hasSeats": true,
        "color": "#dc2626"
      }
    ]
  },
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### GET /v1/lookup/trains/filter

Source: https://railradar.in/docs/filter-trains

Documentation for the Filter Trains API endpoint, including parameters, request example, response example, and error reference.

```APIDOC
## GET /v1/lookup/trains/filter

### Description
Returns active trains matching specified category and type filters.

### Method
GET

### Endpoint
`https://api.railradar.in/v1/lookup/trains/filter`

### Parameters
#### Query Parameters
- **category** (string) - Optional - Train category filter. Allowed values: Premium | Superfast | Express | Passenger | Suburban | Special. Omit for all categories.
- **type** (string) - Optional - Train type filter. Allowed values: vande-bharat | rajdhani | shatabdi | duronto | garib-rath | superfast | express | passenger | local | special. Omit for all types.

### Request Example
```
curl -X GET "https://api.railradar.in/v1/lookup/trains/filter?category=Superfast&type=SF" \
  -H "Authorization: Bearer rr_live_YOUR_API_KEY"
```

### Response
#### Success Response (200)
- **success** (boolean) - Indicates if the request was successful.
- **data** (array) - List of trains matching the filters.
  - **train_number** (string) - Train number.
  - **train_name** (string) - Train name.
  - **category** (string) - Train category.
  - **type** (string) - Train type.
- **meta** (object) - Metadata about the response.
  - **traceId** (string) - Unique trace identifier.
  - **timestamp** (string) - Response timestamp.
  - **executionTime** (number) - Execution time in milliseconds.
  - **source** (string) - Data source.

#### Response Example
```
{
  "success": true,
  "data": [
    {
      "train_number": "12919",
      "train_name": "Malwa SF Express",
      "category": "Superfast",
      "type": "SF"
    },
    {
      "train_number": "12952",
      "train_name": "Mumbai Rajdhani Express",
      "category": "Premium",
      "type": "RAJ"
    },
    {
      "train_number": "22436",
      "train_name": "Vande Bharat Express",
      "category": "Premium",
      "type": "VB"
    }
  ],
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

### Error Reference
- **400 Bad Request** - Invalid parameter format, missing required field, or malformed request syntax.
- **401 Unauthorized** - Missing, expired, or invalid API key in Authorization Bearer header.
- **404 Not Found** - The requested train, station, or PNR record was not found.
- **429 Rate Limited** - Request rate exceeded your plan quota (100 requests/month on free sandbox tier).
- **503 Service Unavailable** - Upstream transit telemetry provider temporarily degraded.

#### Error Response Example (404 Not Found)
```
{
  "success": false,
  "error": {
    "code": "NOT_FOUND",
    "message": "Resource not found (e.g. Train 12919 not found on journey date 2026-06-22)"
  },
  "meta": {
    "traceId": "9772f1c9-6ec6-4d9f-b269-a5210f33ec73",
    "timestamp": "2026-06-22T08:14:00+05:30",
    "executionTime": 5,
    "source": "database"
  }
}
```
```

--------------------------------

### Successful response example (200 OK)

Source: https://railradar.in/docs/station-lookup

Shows the JSON structure returned on success, containing a flat code-to-name dictionary in the data field and metadata including traceId, timestamp, executionTime, and source.

```json
{
  "success": true,
  "data": {
    "INDB": "Indore Junction BG",
    "UJN": "Ujjain Junction",
    "NDLS": "New Delhi",
    "BCT": "Mumbai Central"
  },
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### JSON response example

Source: https://railradar.in/docs/legacy-shipping-find-trains

Shows a successful response with train data including station details, train number, running days, and loading/unloading times.

```json
{
  "success": true,
  "data": [
    {
      "stationCode": "KSV",
      "stationName": "Kosi Kalan",
      "lat": 27.795105,
      "lng": 77.433853,
      "distanceKm": 88.58,
      "totalTrains": 1,
      "trains": [
        {
          "trainNumber": "11906",
          "trainName": "Agra Cantt Express",
          "type": "Mail/Express",
          "runningDays": {
            "mon": true,
            "tue": true,
            "wed": true,
            "thu": true,
            "fri": true,
            "sat": true,
            "sun": true
          },
          "loading": {
            "stationCode": "NDLS",
            "stationName": "New Delhi",
            "arrival": "07:10",
            "departure": "07:20",
            "haltMinutes": 10,
            "day": 2
          },
          "unloading": {
            "stationCode": "KSV",
            "stationName": "Kosi Kalan",
            "arrival": "08:50",
            "departure": "08:52",
            "haltMinutes": 2,
            "day": 2
          }
        }
      ]
    }
  ],
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### cURL request to GET /v1/lookup/stations

Source: https://railradar.in/docs/station-lookup

Sends a GET request to the station lookup endpoint with an Authorization Bearer header. Requires a valid API key (e.g., rr_live_YOUR_API_KEY).

```bash
curl -X GET "https://api.railradar.in/v1/lookup/stations" \
  -H "Authorization: Bearer rr_live_YOUR_API_KEY"
```

--------------------------------

### JSON response example for POST /v1/journeys/plan

Source: https://railradar.in/docs/journey-plan

Shows a 200 OK response with a success flag and data containing two segments (NDLS to BPL, BPL to MMCT) with train details, dates, and a summary. Includes meta information with traceId, timestamp, executionTime, and source.

```json
{
  "success": true,
  "data": {
    "segments": [
      {
        "from": "NDLS",
        "to": "BPL",
        "date": "2026-09-22",
        "plan": {
          "from": {
            "code": "NDLS",
            "name": "NEW DELHI"
          },
          "to": {
            "code": "BPL",
            "name": "BHOPAL JN"
          },
          "date": "2026-09-22",
          "direct": [
            {
              "train": {
                "number": "12002",
                "name": "NDLS SHATABDI",
                "type": "Shatabdi",
                "category": "Shatabdi",
                "classes": [
                  "CC",
                  "EC"
                ]
              },
              "from": {
                "code": "NDLS",
                "name": "NEW DELHI",
                "departure": "06:00",
                "date": "2026-09-22"
              },
              "to": {
                "code": "BPL",
                "name": "BHOPAL JN",
                "arrival": "14:40",
                "date": "2026-09-22"
              },
              "durationMinutes": 520,
              "expectedDelayMinutes": 8,
              "delayKnown": true,
              "reliability": "solid"
            }
          ],
          "itineraries": [],
          "count": 1
        }
      },
      {
        "from": "BPL",
        "to": "MMCT",
        "date": "2026-09-24",
        "plan": {
          "from": {
            "code": "BPL",
            "name": "BHOPAL JN"
          },
          "to": {
            "code": "MMCT",
            "name": "MUMBAI CENTRAL"
          },
          "date": "2026-09-24",
          "direct": [
            {
              "train": {
                "number": "12954",
                "name": "AUGUST KRANTI RAJDHANI",
                "type": "Rajdhani",
                "category": "Rajdhani",
                "classes": [
                  "1A",
                  "2A",
                  "3A"
                ]
              },
              "from": {
                "code": "BPL",
                "name": "BHOPAL JN",
                "departure": "21:15",
                "date": "2026-09-24"
              },
              "to": {
                "code": "MMCT",
                "name": "MUMBAI CENTRAL",
                "arrival": "09:45",
                "date": "2026-09-25"
              },
              "durationMinutes": 750,
              "expectedDelayMinutes": 4,
              "delayKnown": true,
              "reliability": "solid"
            }
          ],
          "itineraries": [],
          "count": 1
        }
      }
    ],
    "count": 2,
    "summary": {
      "stops": [
        "NDLS",
        "BPL",
        "MMCT"
      ],
      "departDate": "2026-09-22",
      "arriveDate": "2026-09-25",
      "totalMinutes": 1270,
      "stayNights": 2
    }
  },
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### cURL request to GET /v1/legacy/stations/all-kvs

Source: https://railradar.in/docs/legacy-all-stations-kvs

Sends a GET request to the legacy endpoint with an Authorization header using a Bearer token. Requires a valid API key (e.g., rr_live_YOUR_API_KEY).

```bash
curl -X GET "https://api.railradar.in/v1/legacy/stations/all-kvs" \
  -H "Authorization: Bearer rr_live_YOUR_API_KEY"
```

--------------------------------

### Successful response example (200 OK)

Source: https://railradar.in/docs/suburban-local-trains

Shows the JSON structure returned on success. The data object maps train numbers to route descriptions. The meta object includes traceId, timestamp, executionTime, and source.

```json
{
  "success": true,
  "data": {
    "90001": "CCG - BORIVALI FAST LOCAL",
    "97001": "CSMT - KALYAN SLOW LOCAL",
    "97003": "CSMT - TITWALA SLOW LOCAL"
  },
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### JSON response example for compressed train lookup

Source: https://railradar.in/docs/compressed-trains-lookup

Shows a successful 200 OK response with a flat string of train data and metadata including traceId, timestamp, executionTime, and source.

```json
{
  "success": true,
  "data": "12919|Malwa SF Express|DADN|SVDK\n12952|Mumbai Rajdhani|NDLS|MMCT\n12002|Bhopal Shatabdi|NDLS|RKMP",
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```

--------------------------------

### cURL example for Journey Overlay API

Source: https://railradar.in/docs/journey-overlay

Send a POST request to the Journey Overlay API with a JSON body containing train-station pairs. Requires an API key in the Authorization header.

```bash
curl -X POST "https://api.railradar.in/v1/journeys/overlay" \  -H "Authorization: Bearer rr_live_YOUR_API_KEY" \  -H "Content-Type: application/json" \  -d '{
    "pairs": [
      {
        "train": "12002",
        "station": "BPL"
      },
      {
        "train": "12954",
        "station": "MMCT"
      }
    ]
  }'
```

--------------------------------

### cURL request to GET /v1/lookup/trains

Source: https://railradar.in/docs/train-lookup

Sends a GET request to the train lookup endpoint with an Authorization Bearer header containing a live API key. The response is a JSON object with a success flag and a data map of train numbers to names.

```bash
curl -X GET "https://api.railradar.in/v1/lookup/trains" \
  -H "Authorization: Bearer rr_live_YOUR_API_KEY"
```

--------------------------------

### JSON response example for train search

Source: https://railradar.in/docs/search-trains

Example 200 OK response from the train autocomplete endpoint. Shows a success flag, an array of train objects with number, name, source, and destination, and meta information including traceId, timestamp, executionTime, and source.

```json
{
  "success": true,
  "data": [
    {
      "number": "12002",
      "name": "Bhopal Shatabdi",
      "source": "NDLS",
      "destination": "RKMP"
    },
    {
      "number": "12004",
      "name": "Lucknow Shatabdi",
      "source": "NDLS",
      "destination": "LJN"
    },
    {
      "number": "12011",
      "name": "Kalka Shatabdi",
      "source": "NDLS",
      "destination": "KLK"
    }
  ],
  "meta": {
    "traceId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-06-22T12:30:00+05:30",
    "executionTime": 38,
    "source": "database"
  }
}
```