85ms avg
GET|/api/v1/trains/:trainNo/chart-vacant

Vacant Berths After Chart Preparation API

Access real-time vacant berths post-charting directly from online reservation charts. Coach-by-coach layout, current booking berths, and TTE allotment data.

Live Protocol Demo

Production headers and authentic PRS gateway response.

GET/api/v1/trains/12557/chart-vacant?boardingStation=GKP&date=2026-10-24&class=ALL
curl -X GET "https://api.irctc.dev/api/v1/trains/12557/chart-vacant?boardingStation=GKP&date=2026-10-24&class=ALL" \
-H "x-api-key: your_api_key"
200 OK·application/json
latency: 85ms avg
{
"success": true,
"trainNumber": "12557",
"trainName": "SAPT KRANTI EXP",
"boardingStation": "GKP",
"from": "MFP",
"to": "ANVT",
"date": "2026-10-24",
"chartStatus": {
"isChartPrepared": true,
"firstChartTime": "2026-10-24 08:40:47",
"remoteStation": "GKP",
"nextRemoteStation": "LKO"
},
"totalVacantBerths": 14,
"summaryByClass": {
"1A": 0,
"2A": 2,
"3A": 5,
"3E": 3,
"SL": 4
},
"coaches": [
{
"coach": "A1",
"class": "2A",
"position": 1,
"vacantBerths": 2
},
{
"coach": "B1",
"class": "3A",
"position": 3,
"vacantBerths": 5
},
{
"coach": "M1",
"class": "3E",
"position": 8,
"vacantBerths": 3
},
{
"coach": "S1",
"class": "SL",
"position": 10,
"vacantBerths": 4
}
],
"source": "irctc-api",
"syncedAt": "2026-10-24T07:36:22.920Z",
"_time": 0.085
}

Engineered for Railway Throughput

High-throughput PRS reservation engine connectivity with sub-second Redis caches and 99.9% uptime reliability.

Direct Gateway Architecture

Multi-hop routing & telemetry
Dedicated PRS Socket

Queries route through high-speed edge clusters across Indian data center zones with direct PRS gateway connectivity and sub-millisecond dispatch.

HOP_TELEMETRY // DEDICATED_SOCKETTOTAL_BUDGET: 85ms avg
01Edge Ingress
12ms
02Edge Router
< 2ms
03Central PRS Tunnel
85ms avg
Ingress: ~15%Edge: <5%PRS Core: ~80%

Production SLAs & Latency

Deterministic throughput backed by enterprise uptime guarantees.

Latency Benchmark85ms avg
Uptime SLA99.9%
Rate Limits1,000 req/min
Cache Strategy30s Real-Time Sync
01 // Capability

Zero Competitor Parity

No other commercial API gateway exposes clean JSON structured vacant berth data post-charting. Give your travel app a unique market moat.

02 // Capability

Coach Composition & Layout

Includes full train rake configuration with coach positions (A1, B1, S1) and vacant counts per coach.

03 // Capability

Current Booking Intelligence

Empower users to book unallocated berths at station current counters or IRCTC app after charting.

Parameters Specification

Query and path parameters for /api/v1/trains/:trainNo/chart-vacant

trainNostringin: PATH
required

5-digit Indian Railways train number (e.g. 12557).

Example:12557
boardingStationstringin: QUERY
required

Boarding station code (e.g. GKP).

Example:GKP
datestringin: QUERY
optional

Journey date in YYYY-MM-DD or DD-MM-YYYY format (defaults to current date).

Example:2026-10-24
classstringin: QUERY
optional

Travel class code (1A, 2A, 3A, 3E, SL, or ALL). Defaults to ALL.

Example:ALL
Response Status:
200 OK 400 Bad Request 404 Not Found 503 Upstream Maintenance

Frequently Asked Questions

Technical specs regarding IRCTC session lifetime, authentication, and quotas.

First reservation chart is prepared ~4 hours prior to train origin departure. The final chart is prepared 30 minutes before departure.
Bot Blueprint

How to Build a Telegram Alert Bot for Vacant Berths After Chart Preparation

Step-by-step tutorial on building a Telegram bot to get alerted when train charts are prepared and vacant berths open for IRCTC Current Booking.

Read Tutorial

Related Railway Endpoints

$npm i irctc-api

Integrate Vacant Berths After Chart Preparation API

Integrate live Indian Railways data into your production or staging stack. 10,000 free sandbox calls included.