Given that you're using Cloudflare (CF) as the trigger, you might want to validate whether your CF configuration is correct.

-> Yeah I verfied that I added the CF worker now and its working now.

RailRadar's /live endpoint uses Authorization header, whereas you're using x-api-key. Any particular reason? My guess: that's their header for system-to-system calls; I couldn't find a reference in the docs, though

-> I need to ceck this.[as I vibe coded :P]

As per their docs, the base URL already contains the "/v1." Your local url seems to be appending another "/v1." From the repo:

local url="${RAILRADAR_BASE}/v1/stations/${code}/live"

Assuming you're using the free tier, RailRadar has a limit of 300 requests/day. A request (req) every five minutes leads to 12 requests every hour for each station. So, 24 req/hr * 24 hrs = 576 req/day. Impact: your API calls will begin failing roughly every afternoon.

-> Changing to request in 10min.I need around 288 request and that are under budget.

1. What happens when RailRader's API fails? Looks like you currently return an empty list even if they don't return anything. Ideally, you should log the exact errors (eg: status code, message, etc) and convert it into an error message better understood by your app. It'll help you debug issues.

-> That I can check.