68ms avg
GET|/api/v1/pnr/:pnr

Real-Time PNR Status API

Sub-100ms Indian Railways passenger confirmation, coach & berth allocation, and chart preparation status with zero scraping headaches.

Live Protocol Demo

Production headers and authentic PRS gateway response.

GET/api/v1/pnr/2265248473
curl -X GET "https://api.irctc.dev/api/v1/pnr/2265248473" \
-H "x-api-key: your_api_key"
200 OK·application/json
latency: 68ms avg
{
"success": true,
"data": {
"pnr": "2265248473",
"trainNumber": "15726",
"trainName": "ANVT NJP EXP",
"from": {
"code": "MFP",
"time": "Nov 23, 2026 10:05:00 AM"
},
"to": {
"code": "NJP",
"time": "Nov 23, 2026 6:45:00 PM"
},
"journeyDate": "Nov 23, 2026 10:05:00 AM",
"class": "SL",
"quota": "GN",
"chartStatus": "chart not prepared",
"passengers": [
{
"number": 1,
"status": "CNF",
"coach": "S4",
"seat": "65",
"berth": "LOWER BERTH",
"raw": "CNF/S4/65/LB"
},
{
"number": 2,
"status": "CNF",
"coach": "S4",
"seat": "66",
"berth": "MIDDLE BERTH",
"raw": "CNF/S4/66/MB"
}
],
"updatedAt": "2026-10-24T07:40:06.056Z",
"source": "irctc-api"
},
"source": "irctc-api",
"_time": 0.082
}

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: 68ms avg
01Edge Ingress
12ms
02Edge Router
< 2ms
03Central PRS Tunnel
68ms avg
Ingress: ~15%Edge: <5%PRS Core: ~80%

Production SLAs & Latency

Deterministic throughput backed by enterprise uptime guarantees.

Latency Benchmark68ms avg
Uptime SLA99.95%
Rate Limits1,000 req/min
Cache Strategy60s Redis Cache
01 // Capability

Deep Passenger Manifest

Instant parsing of all ticket holders with discrete booking status, current confirmation, coach code, and berth assignment (Lower, Middle, Upper, Side Lower).

02 // Capability

Charting Status Detection

Accurate boolean flags detecting whether 1st chart or final chart has been prepared at the train origin station.

03 // Capability

Zero Captcha / Direct Sync

Bypass Cloudflare and IRCTC session rotation limits with our automated rotating residential IP pool.

Parameters Specification

Query and path parameters for /api/v1/pnr/:pnr

pnrstringin: PATH
required

10-digit authentic Indian Railways PNR number without hyphens or spaces.

Example:2265248473
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.

Our average round-trip execution latency is under 80 milliseconds. Cached queries resolve in sub-5ms through globally distributed Redis edge instances.
Production Guide

How to Check Indian Railway PNR Status Programmatically

Step-by-step tutorial with complete Node.js and Python code samples for PNR decoding, berth allocations, and charting state.

Read Tutorial

Related Railway Endpoints

$npm i irctc-api

Integrate Real-Time PNR Status API

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