JSON returned by API endpoint v1 timingsByCity is not matching the demo app play link about api.aladhan.com HOT 5 CLOSED

For March 11 2023 The "play" link Fajr time is displayed as 5:13 am which matches expectation

https://aladhan.com/play/Corvallis/OR,%20USA

However, I am invoking the timingsByCity with the following code:

let URL = `https://api.aladhan.com/v1/timingsByCity?country=${Country}&region=${Region}&city=${City}&method=${Method}&adjustment=${HijriCorrection}`
this.Load(URL)

actual request...

https://api.aladhan.com/v1/timingsByCity?country=US&region=Oregon&city=Corvallis&method=2&adjustment=1

and I get the following JSON with Fajr time as 5:00 am

what parameter(s) am I missing to match the timings displayed in the play link? Also, I don't see a parameter regarding whether to use the system time or cloud time? if that matters? Thank you.

You need to use the correct method - ISNA - to get the same result.

from api.aladhan.com.

I am posting method=2 in my example above
https://api.aladhan.com/v1/timingsByCity?country=US&region=Oregon&city=Corvallis&method=2&adjustment=1
The returned JSON also says ISNA ?

from api.aladhan.com.

Where did you get the region query parameter from? The API only supports state, not region.

from api.aladhan.com.

Back in issue #52 I had asked whether "region" was an accepted parameters. I must have gotten side-tracked with your fix to a different issue and never double checked the returned timings where correct.
Because I started using a geolocation service returning "region" I must have "believed" is was accepted by this API.
TODO: Perhaps your API can return an error about illegal parameters in the future.
The following is now returning the expected times
https://api.aladhan.com/v1/timingsByCity/11-03-2023?country=US&state=Oregon&city=Corvallis&method=2&adjustment=1

Thank you for the catch, much appreciated.
Jazaakum Allahu Khayran! and Ramadhan Mubaarak and Kareem !!!

from api.aladhan.com.

Back in issue #52 I had asked whether "region" was an accepted parameters. I must have gotten side-tracked with your fix to a different issue and never double checked the returned timings where correct. Because I started using a geolocation service returning "region" I must have "believed" is was accepted by this API. TODO: Perhaps your API can return an error about illegal parameters in the future. The following is now returning the expected times https://api.aladhan.com/v1/timingsByCity/11-03-2023?country=US&state=Oregon&city=Corvallis&method=2&adjustment=1

Thank you for the catch, much appreciated. Jazaakum Allahu Khayran! and Ramadhan Mubaarak and Kareem !!!

Illegal query parameters are simply ignored - throwing errors for those is bordering an extreme in my humble opinion. Sometimes client side JavaScript calls append a timestamp or random query parameter to bypass caching, and that would result in failing calls.

It's a public API, so flexibility is always important. But reading the documentation is always the simplest way to get it right.

By the way, you can also just simply use the timingsByAddress endpoint, and just pass one string in the address query parameter.

JazakAllah for the Ramadan wishes! May yours be full of blessings too!

from api.aladhan.com.