We are delighted to be able to announce the launch of our new API service.
You can find documentation for the new API service at realtimetrains.github.io/api-specification. You can request a token for the new API on our new portal at api-portal.rtt.io.
The new API has a number of improvements including a new more usable JSON structure, OpenAPI specification and much-requested ISO-8601 datetimes. We’ve been working on this for just over a year and slowly migrating many of our production systems to make use of it. Underneath the hood, RailMiles, our forthcoming apps, and a few components of the Realtime Trains website are now making use of this API platform. We are confident that this is a significant improvement over the current version and, internally, have found it much easier to use than the older versions!
The new API is rate limited, enforced at API level, and the base limits are 30 per minute, 750 per hour, 9000 per day and 30000 per week. We are happy to support higher rate limits based on your use case - please get in touch with our support team if this applies to you.
This new platform replaces both of our existing API services at api.rtt.io and secure.realtimetrains.co.uk. These services are now deprecated and will be shut down in 6 months and 12 months respectively on 30 September 2026 and 31 March 2027 respectively.
Support for personal users of the API is available via the community on our Discord server. Commercial support is available through our support teams as now.
