Indian rail data, one stable contract

Live stations, trains, availability, fares, chart intelligence, and async analysis through one authenticated v1 API.

Build with RailCore's Indian railway API: station, train, journey, availability, fare and chart endpoints with complete guides, an error reference and an interactive playground.

Base URL https://ir.railcore.tech/v1. Authenticate with an X-RailCore-Key header. Every response uses a shared envelope, and every endpoint documents its scope, credit cost and error codes.

Guides

• Quickstart — Make the first authenticated request.
• Authentication — API keys, scopes, expiry, and IP allowlists.
• Using the playground — Test safely with your own key.
• Response envelope — Shared success, error, metadata, and headers.
• Errors and retries — Stable codes and retry decisions.
• Rate limits — Minute and daily budgets with headers.
• Credits and billing — Costs, settlement, renewals, and batches.
• HMAC signing — Payload canonicalization and replay protection.
• Error code catalog — Every public error code in one table.
• Header reference — Request, rate, credit, and trace headers.
• Changelog — API and documentation release history.

Authentication

Every request carries your key in an X-RailCore-Key header. Keys are scoped per endpoint family, can be rotated, and may be restricted to an IP allowlist. Requests that change state can additionally be HMAC-signed. See authentication and HMAC signing.

Standard response envelope

Every endpoint returns the same envelope, so a client written against one operation already understands the rest: a success flag, the payload under data, and metadata carrying the request id and timing. Errors use the same shape with a stable machine-readable code rather than prose. Full reference in response envelope, and the complete code list in the error code catalog.

Rate limits and credits

Usage is metered in credits, and each endpoint documents its own cost and the plans it is available on. Per-minute and daily budgets are enforced, and every response reports the remaining quota in headers so a client can back off before it is throttled. See rate limits, credits and billing and the header reference.

API reference — 32 endpoints

Stations (4)

• Search stations — GET /v1/stations/search. Find stations by code, city, name, or alias.
• Get station — GET /v1/stations/{station_code}. Resolve one canonical station record.
• Live station board — GET /v1/stations/{station_code}/live. Arrivals and departures in a rolling live window.
• Station board alias — GET /v1/stations/{station_code}/trains. Compatibility alias for the live station board.

Trains (8)

• Search trains — GET /v1/trains/search. Search trains by name or number.
• Get train — GET /v1/trains/{train_number}. Resolve one canonical train record.
• Train schedule — GET /v1/trains/{train_number}/schedule. Get the full scheduled train movement.
• Booking stops — GET /v1/trains/{train_number}/stops. Get booking-relevant stops only.
• Full train route — GET /v1/trains/{train_number}/route. Get stops and pass-through stations.
• Coach position — GET /v1/trains/{train_number}/coach-position. Get coach composition from the engine.
• Live train tracking — GET /v1/trains/{train_number}/live. Track a train with delay and next-stop context.
• Detailed running status — GET /v1/trains/{train_number}/running. Get detailed station-by-station train running updates.

Journeys (3)

• Trains between stations — GET /v1/routes/trains. Find trains serving a route on a date.
• Journey search — GET /v1/journeys/search. Search and rank route options for a journey UI.
• Compare journeys — POST /v1/journeys/compare. Compare up to five route queries in one request.

Availability (4)

• Seat availability — GET /v1/availability/seats. Check live availability for one train and class.
• Batch seat availability — POST /v1/availability/seats/batch. Check up to 25 train and class combinations.
• Availability calendar — GET /v1/availability/calendar. Inspect availability across upcoming dates.
• Available classes — GET /v1/availability/classes. List classes offered by a train on a route.

Fares (3)

• Fare estimate — GET /v1/fares/estimate. Get reserved fare by class for a train segment.
• Search fares — GET /v1/fares/search. Compare fares across trains on a route.
• Unreserved fare — GET /v1/fares/unreserved. Query UTS journey and season-ticket fares.

Charts (4)

• Chart status — GET /v1/charts/status. Check whether chart one or chart two is prepared.
• Vacant berths — GET /v1/charts/vacant-berths. Find post-chart berth vacancies by coach and class.
• Vacant berth hopping — GET /v1/charts/vacant-berths/hopping. Build a same-train berth chain when no berth covers the full route.
• Route vacancy scan — GET /v1/charts/vacant-berths/route-scan. Rank every route train by chart vacancy and hopping coverage.

Jobs (6)

• Submit route-scan job — POST /v1/jobs/route-scan. Run route scanning asynchronously.
• Submit hopping job — POST /v1/jobs/hopping. Run berth-hopping analysis asynchronously.
• Get job — GET /v1/jobs/{job_id}. Poll status and retrieve a completed result.
• Cancel job — DELETE /v1/jobs/{job_id}. Cancel a pending or processing job.
• Stream job progress — GET /v1/jobs/{job_id}/stream. Receive progress and terminal state over SSE.
• List jobs — GET /v1/jobs. List recent jobs with optional filters.

What the RailCore Indian Railways API covers