railworks
railworks reads Iarnród Éireann's [planned engineering works page](https://www.irishrail.ie) every 6 hours and turns it into structured, queryable data: which…
Logistics & shipping#transportation
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
railworks reads Iarnród Éireann's planned engineering works page
every 6 hours and turns it into structured, queryable data: which days, which stations,
what happens there, and how that changed over time. It's read-only, unauthenticated and
cacheable.
> railworks is not affiliated with or endorsed by Iarnród Éireann. The data is
> machine-read from their page and may be wrong: check the source before travelling.
Quick start
Subscribe a calendar to one station. One all-day event per affected day, e.g.
"No trains at Woodbrook":
webcal://railworks.paddez.com/v1/feeds/notices.ics?station=WBROK- Apple Calendar / Outlook: open the
webcal://link, or add it as a subscribed calendar. - Google Calendar: Other calendars → From URL, using
https://instead ofwebcal://.
Google refreshes subscriptions only every several hours.
- Narrow it with
&line=dart(stations on the DART) or&group=DART%20Services(only
notices published under DART).
Ask whether a station is affected, and when:
curl https://railworks.paddez.com/v1/stations/WBROK/daysList what's planned (today to 90 days ahead by default):
curl "https://railworks.paddez.com/v2/notices?line=dart"Follow every change without missing any: see Polling for changes.
Client libraries
Python: pyrailworks (PyPI)
has sync and async clients, Pydantic models, RFC 9457 errors as exceptions, and cursor
handling for the change log:
pip install pyrailworksfrom pyrailworks import RailworksClient
with RailworksClient() as client:
for day in client.get_station_days("WBROK").days:
print(day.date, day.effect.value) # 2026-10-03 no_serviceEvery endpoint below has a Python example. Anything else can use the
OpenAPI document with a client generator.
Concepts
| Term | Meaning |
|---|---|
| Works Notice | One dated block of engineering works, as published under one Service Group: a set of days, the published text, and what it does to the service. Identified across page updates by a stable id. |
| Service Group | A heading on the works page ("DART Services", "Rosslare Services") under which notices are published. |
| Line | The stations one Service Group's trains serve, in order along its branches, named after the group (dart, northern-commuters, …). |
| Build | One published version of the works page, identified by when upstream built it (built_at). |
| Revision | A change to a notice's published text between builds, identity unchanged. A trim is a revision that drops days that have passed; an extension is one that adds days and keeps every day still to come. |
| Works Segment | A track section where works take place ("between Dromod and Sligo"), expanded to every station in between. |
| Effect | A station- or section-level consequence: no_service, station_closed, bus_replacement, reduced_service, other. |
| Service Alteration | A change to one train (cancelled, bus-replaced, terminating short, …). |
| Station Day | One date a station is affected, with the strongest effect there. The same closure published under DART and Rosslare is one Station Day. |
| Expired / Withdrawn | A notice leaves the page when its days pass (expired, the normal end of life) or while it still had days to come (withdrawn). Nothing is ever deleted. |
How notices are read
- Dates come from the heading only. The year is inferred from weekday names (e.g.
"Saturday 24 October" is 2026), and weekday typos are repaired when exactly one date fits.date_inference shows how.
- Where comes from the notice's "engineering works between X and Y" sentence and from an
LLM (Gemini) that structures the prose. Every LLM item is checked before it's used: its
quote must be verbatim in the notice, every station it names must appear in the text and be
a known station, and every time must appear in the text. Anything else is dropped and
lowers confidence.
- Extraction is asynchronous. A new notice is served at once with `extraction.status:
pending and fills in within minutes; an extracted` change event says so.
confidence(0–1): the heading parsed to days +0.5, a validated works segment +0.3,
every named station resolved +0.2; −0.1 for each weekday repair, unresolved date conflict,
prose that disagrees with the heading, or LLM item that failed validation.
Nothing is hidden by default (min_confidence=0).
Polling for changes
/v1/changes is an append-only log of created, revised (with trim or extended), expired,withdrawn and extracted events behind an opaque cursor. Start with ?since= once, then
always pass the previous response's next:
cursor=$(curl -s…Endpoints 26
Notices
- GETList Works Notices
/v1/noticesDeprecated. Deprecated: gone on 1 December 2026 (Sunset 2026-12-01T00:00:00Z). It serves Iarnród Éireann's published text, which railworks no longer… - GETGet one Works Notice
/v1/notices/:idDeprecated. Deprecated: gone on 1 December 2026 (Sunset 2026-12-01T00:00:00Z). It serves Iarnród Éireann's published text, which railworks no longer… - GETGet a notice's upstream HTML
/v1/notices/:id/rawDeprecated. Deprecated: gone on 1 December 2026 (Sunset 2026-12-01T00:00:00Z). It serves Iarnród Éireann's published text, which railworks no longer… - GETFollow the change log
/v1/changesEvents after an opaque cursor, oldest first. Pass after (a previous next), or since for a first call only. Each event is returned exactly once when you follow… - GETList Works Notices (v2)
/v2/noticesWorks Notices with any day in the window, as /v1/notices lists them but without Iarnród Éireann's text: each notice has railworks' own title and summary… - GETGet one Works Notice (v2)
/v2/notices/:idThe notice in full: its title and summary, Day Sections (days only), Works Segments, Effects, per-train Service Alterations and revision history, with every… - GETFollow the change log (v2)
/v2/changesThe same change log as /v1/changes (its events carry no upstream text), with the same cursors: a cursor from either works on both. Each event names a…
Stations
- GETList stations
/v1/stationsEvery Irish Rail station served by timetabled trains, with its Lines and position on each. Refreshed daily from the TFI GTFS feed and Irish Rail's station list. - GETGet one station
/v1/stations/:codeAlias codes (other Irish Rail codes for the same station, e.g. ADAMF) redirect to the canonical code. - GETIs this station affected, and when?
/v1/stations/:code/daysOne Station Day per affected date in the window, deduplicated across Service Groups, with the strongest effect at the station (no_service > station_closed >… - GETList stations (v2)
/v2/stationsThe same as /v1/stations. - GETGet one station (v2)
/v2/stations/:codeThe same as /v1/stations/{code}. Alias codes redirect to /v2/stations/{canonical code}. - GETIs this station affected, and when? (v2)
/v2/stations/:code/daysThe same Station Days as /v1/stations/{code}/days; alias codes redirect within /v2.
Feeds
- GETCalendar feed
/v1/feeds/notices.icsAn iCalendar (RFC 5545) feed to subscribe to. All events are all-day; a stated time of day goes in the title. With station: one event per Station Day at that… - GETCalendar feed (v2)
/v2/feeds/notices.icsThe same calendar as /v1/feeds/notices.ics, byte for byte: calendar text was already railworks' own wording. Both stay; /v1/feeds/notices.ics isn't retired,…
Service
- GETHealth and things needing a human
/v1/healthDeprecated. Deprecated: gone on 1 December 2026 (Sunset 2026-12-01T00:00:00Z). It serves Iarnród Éireann's published text, which railworks no longer… - GETThis document
/v1/openapi.yaml - GETHealth and things needing a human (v2)
/v2/healthThe same as /v1/health, except that each listed notice is named by its generated title, not its published heading. The container healthcheck (railworks… - GETThis document (v2)
/v2/openapi.yamlThe same document as /v1/openapi.yaml, which describes both versions. - GETHome page
/Subscribe to a station's calendar, see its upcoming affected days, and what's planned in the next four weeks. Built on this API. - GETThis documentation, rendered
/docs
Site
- GETRobots rules
/robots.txtLets crawlers index the pages and keeps them off the API. - GETSitemap
/sitemap.xmlThe pages, with the home page's last change. - GETLLM summary
/llms.txtA plain-Markdown summary of the API for AI tools (llmstxt.org). - GETSocial card
/og.pngThe 1200×630 image shown when the site is shared. - GETFavicon
/favicon.svgThe site icon.
API details
- Base URL
https://railworks.paddez.com- Authentication
- None declared in the description
- Operations
- 26 operations on 26 pathsGET 26
4 marked deprecated - Main resources
- Notices 7Service 6Stations 6Site 5Feeds 2
- Response formats
application/jsonapplication/yamltext/calendartext/html- Description format
- OpenAPI 3.1.0, API version
1 - Links
- OpenAPI document
- Listed from
- Paddez's published OpenAPI description
How to test the railworks in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the railworks collection, without the publisher's secrets.
- Add your credentialsOpen the collection's variables or an environment and enter your API key or token, if the API needs one.
- Send a requestPick an endpoint, for example “List Works Notices” (GET /v1/notices), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the railworks?
railworks reads Iarnród Éireann's [planned engineering works page](https://www.irishrail.ie) every 6 hours and turns it into structured, queryable data: which… It is listed under Logistics & shipping and has 26 endpoints.
Who publishes the railworks?
It is listed from Paddez's public API description (an OpenAPI document), not published by Paddez on Swastik Codes. Anyone who controls railworks.paddez.com can claim the profile by adding a DNS TXT record.
What is the base URL of the railworks?
Requests go to https://railworks.paddez.com. Endpoint paths are added to this base URL.
How do I authenticate with the railworks?
Its OpenAPI description does not declare an authentication scheme. Some endpoints may be open; check the provider's documentation before relying on that.
How many endpoints does the railworks have?
26 operations on 26 paths (26 GET). The largest groups are Notices, Service, Stations, Site.
Is forking the railworks free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.