Journey API internal errors


We have some routine tasks that have started to experience 500 internal error exceptions today.

Example call:

The query filters for National Rail services between Heathrow T5 and Paddington.

Any ideas?

Many thanks,


A 500 normally means you’re hammering the API with too many requests.

Perhaps you can cache the result for a bit at the client end?

Hi Brian,

Thanks for the reply. The problem has resolved itself.
We’ve been slow and steady on our usage for over a year, and the 500’s just started, and then went away again.



1 Like

@TimH I’m pleased to hear the issue has cleared itself.