API result does not indicate non-existent withdrawal request IDs

[asatzger]

For withdrawal request IDs above the latest one (see this Dune query; currently at c. 74045), the API response does not indicate that the withdrawal request ID does not exist and instead returns the default result for calling /calculate without a specified amount

(venv) ➜  lido-withdrawals-api-data git:(main) ✗ curl https://wq-api.lido.fi/v2/request-time/calculate
{"requestInfo":{"finalizationIn":415604000,"finalizationAt":"2025-03-15T12:30:22.723Z","type":"exitValidators"},"status":"calculated","nextCalculationAt":"2025-03-10T17:05:00.306Z"}%                                                                                     
(venv) ➜  lido-withdrawals-api-data git:(main) ✗ curl https://wq-api.lido.fi/v2/request-time\?ids\=7400000
[{"requestInfo":{"finalizationIn":415598000,"finalizationAt":"2025-03-15T12:30:22.734Z","type":"exitValidators","requestId":"7400000"},"status":"calculating","nextCalculationAt":"2025-03-10T17:05:00.306Z"}]%                                                            ```

[Tarens2]

Basically I agree that it is not very obvious response from API but it is actually different see field status it is calculated or calculating.

calculating is returned for requests which API doesn't know yet.

The API doesn't catch instantly withdrawal requests. It checks statuses of withdrawal request each 5 min so there might be a gap before request will be available in API.

So in this case when you request non existed yet 7400000 request this just return calculating and default value, that is how we designed API.

@DiRaiks Maybe we should think how to make API more obvious