Indian Railways API documentation, honest about freshness.

Live Train Status

Live running status for one train on one journey date: running state, current/previous/next station, GPS position with its observed time, speed, delay, ETA, route progress and exceptions. Every response carries honest freshness (LIVE, RECENT or STALE) and a confidence level (HIGH, MEDIUM or LOW) instead of guessed data.

Train Schedule

Scheduled journey information for a train on a given date: origin, destination, departure and arrival times, travel time, travel classes and running days. This is timetable data, not live movement — pair it with Live Train Status for position and delay.

Train Route

Station-by-station route for a train on a given date: every stop with scheduled and actual arrival/departure times, halt flag, journey day, platform, cumulative distance and coordinates.

Search Trains

Find trains by number or partial name in one request. Returns matching trains with their number, name and origin/destination codes plus the result count.

Station by Code

Resolve a station code such as NDLS to its full record: canonical name, known aliases, coordinates, state, zone and division.

Search Stations

Find stations by partial name or code. Returns matching station records with coordinates and the result count.

Station Live Board

Arrivals and departures for one station over a rolling window around now: every train with its scheduled times at this station, platform, expected (delayed) times, delay minutes and a live state such as at-station, upcoming, departed or scheduled. This is the departures board, driven by the same live observations as the train status endpoint.

PNR Status

Booking record behind a 10-digit PNR: train, journey date, class, quota, fare paid at booking, chart status and every passenger's current status with coach and berth. Reported exactly as the reservation system returns it — CNF, RAC and WL are never reinterpreted, and a flushed or expired PNR returns 404 PNR_NOT_FOUND.

Coach Composition

Rake formation for a train: coach position order from the locomotive, per-class summary counts, reversals where the train changes direction, and per-leg formations for trains that run different rakes on different sections. Berth layouts and per-station formations are available as opt-in extras because they are large.

Fare Enquiry

Itemised fare quote for one train, one date, one travel class and one quota: base fare, reservation and superfast charges, GST, tatkal and dynamic components, and the total, together with the distance. Every charge comes from the fare engine as reported — nothing is rounded, estimated or filled in.

Platform Numbers

Platform allocation for a train at every station the source has reports for: the platform label, the source's own confidence tag (a share such as "88%" or the word "most") and the feedback count behind it, exactly as upstream reported them. Stations without a usable report are omitted rather than guessed, and trainName stays null when the source names no train.

Service Health

Liveness check for the API itself: service name, running version, environment and the current server time. Useful for monitoring and for confirming your key and network path work.

Service Version

Returns just the service name and the running version — the smallest possible payload for build scripts, dashboards and support reports.

Data Coverage

What this dataset really covers, published honestly: per-capability availability with how it was verified and when, plus dataset records such as the station list. Nothing here claims 100% coverage.

Provider Health

Status of each upstream data provider: state, measured latency, last success and last failure times, error count, configured capabilities and a short note. This is how the API stays transparent about where its data comes from.