API Terms of Use & Attribution
_Last updated: 1 October 2026_
These terms govern your access to and use of LopoRail's publicly
accessible Application Programming Interfaces ("the APIs"). By accessing or
using the APIs you accept these terms.
1. The APIs and who operates them
1.1 These Terms govern your access to and use of LopoRail's publicly
accessible APIs, including but not limited to our document endpoints
(/wp-json/loporail-legal/v1/docs and /docs/{slug}) and any future public
API endpoints deployed by the platform.
1.2 The APIs are read-only. No endpoint accepts user content, and no
endpoint may be used to modify the Service.
1.3 The APIs are operated by LopoRail. Contact: [email protected].
2. Licence to use
2.1 Subject to these terms, LopoRail grants you a limited,
non-exclusive, non-transferable, revocable licence to access the APIs and to
use the returned data as part of your own application.
2.2 The licence does not include the right to resell API access, to offer a
substantially similar competing data service, or to republish the content in
full as your own.
2.3 We may suspend or terminate access at any time for breach of these terms,
for abuse of the Service, or for operational reasons.
2.4 Bulk and structured dataset exports. A paid Enterprise (bulk)
licence may include structured dataset exports ("dumps") and historical data.
Where you hold such a licence, you may download and use those datasets under
that licence and these terms. Exported datasets remain subject to §2.2 except
as your Enterprise licence expressly permits — in particular there is **no
onward sale or redistribution** of exported data, and no use to build a
substantially similar competing service, without our written agreement.
**Upstream credits required by §3.3 — including the Open Government Licence
v3.0, Network Rail and Rail Delivery Group notices — must always travel with
any exported file, and cannot be waived.** Fares/routeing data is excluded
from bulk exports (§3.5(b)). For bulk-export licensing enquiries,
3. Attribution (required)
3.1 Any display of data obtained through the APIs must carry visible
attribution in the form:
Data © LopoRail — sourced via the LopoRail API
3.2 Where the display is interactive (web or in-app), the attribution must
link to https://loporail.com. Where the display is static (print or PDF), the
attribution must include the full site address. Our own "Data © LopoRail"
credit may be relaxed only under a negotiated Enterprise licence; the upstream
credits in §3.3 can never be waived.
3.3 Upstream data and third-party licences. Where data is derived from
upstream partners, you must also preserve all original copyright notices,
including but not limited to: *"Contains public sector information licensed
under the Open Government Licence v3.0 via Network Rail and the Rail Delivery
Group (Rail Data Marketplace)."* A full, dynamically updated list of
third-party data providers and their licensing terms is at
/data-sources/ and is incorporated into these terms by
reference.
3.4 You must not remove, obscure, or alter attribution, copyright notices, or
licence statements included in API responses.
3.5 Dataset-specific licences. Different datasets carry different upstream
terms:
(a) Timetable and real-time train-running data (Darwin) is provided under
the National Rail Enquiries Open Government Licence (NRE OGL). You may use
it commercially and adapt its format, but you must display the specified NRE
attribution statement and link to the licence, must **not alter forecast
arrival/departure times, and must not cache or display stale real-time
data** ("Time-Bound Data").
(b) Fares and routeing data (DTD / Rail Settlement Plan) is provided under
the RSP Data Licence, which is proprietary. You must present fares
impartially (no bias toward any operator or transport mode), must **not
add, modify or delete** the source data without written authority, and must
not sub-license it. Selling tickets requires a separate retail licence and
RDG accreditation. Fares data is excluded from any bulk export under §2.4.
3.6 Community-sourced feeds. A number of feeds are community-sourced
(currently: **Switzerland, Germany (IRIS), France, Japan (Toei), Montenegro,
Slovenia, Ukraine, and US LIRR / MNR). These are unofficial, not
affiliated with the operator, and provided as-is**. Their per-source
attribution and licence are published at /wp-json/loporail/v1/providers and
live.loporail.com/api/feeds, and you must **preserve the attribution we
display**. Where a source states a licence (for example Montenegro ODbL-1.0,
Slovenia CC BY-SA 4.0) that licence governs redistribution; where **no licence
is stated (for example Ukraine) we use the data in good faith**, without
warranty, and do not authorise its redistribution — such data is
excluded from bulk exports.
4. Fair use
4.1 API usage is subject to fair-use limits to ensure platform stability.
While we do not publish static numeric limits in these Terms, we reserve the
right to enforce rate-limiting thresholds, throttle access, or suspend API
keys immediately and without notice where usage patterns negatively impact
our infrastructure or exceed reasonable volume expectations.
4.2 You must cache responses where practical and must not poll the APIs at
intervals that a cached copy would make unnecessary.
4.3 Standard browser integrations must identify themselves honestly and must
not circumvent rate limits, authentication, or other protective measures.
5. No warranty
5.1 The APIs and their content are provided "as is" without warranty of any
kind. Availability, accuracy, and completeness are not guaranteed; legal
documents may change at any time, and consumers should re-fetch rather than
permanently cache.
5.2 Reliability tiers. Feeds are tiered as official, self-built or
community; each response states its source's tier.
5.3 Upstream is best-effort. Third-party and upstream feeds are provided
best-effort: we give no guarantee of uptime, completeness or accuracy,
and a feed may change or stop at any time.
5.4 What our SLO covers. Any published availability service level (for
example 99.9%) applies to API availability only — it does not warrant
the correctness, completeness or timeliness of the underlying data, and it
does not apply to feeds with a community reliability tier (currently 14
sources — Armenia, Austria, Switzerland, Georgia, Greece, South Korea,
Lithuania, Montenegro, Poland, Serbia, Slovenia, Türkiye, Ukraine, and Los
Angeles (Metrolink) — listed with their tier at live.loporail.com/api/feeds).
5.5 Community feeds may be less reliable or less current. **Do not rely on
the APIs for safety-critical decisions.**
6. Liability
6.1 To the maximum extent permitted by law, our aggregate liability for the
free public API is nil (£0), as this service is provided free of charge.
For any paid, commercial, or Business API tier, our liability shall be
strictly limited to the total fees paid by you to us for the specific API
service during the twelve (12) months preceding the event giving rise to
liability, unless otherwise specified in a separate written commercial
agreement.
7. Changes
7.1 We may change these terms, the APIs, or their content at any time.
Continued use after a change constitutes acceptance. The "last updated" date
above reflects the current version.
8. Governing law and disputes
8.1 These terms are governed by the laws of England and Wales, and the
courts of England and Wales have exclusive jurisdiction, except that (a)
consumers may also bring proceedings in their country of residence under
mandatory local law; and (b) nothing deprives you of mandatory consumer
protections in your jurisdiction. This mirrors the approach in our
Advertising Terms, §13.