Rapid account: null

/ meezaan

إِنَّا لِلَّهِ وَإِنَّا إِلَيْهِ رَاجِعُونَ

Discussões

14
Title
Created at (Click to sort ascending)
A
2
Which request? Have you seen the docs on aladhan.com/prayer-times-api? Wed 5:46 10/5/23
A
3
This is not the case - see https://api.aladhan.com/v1/timingsByCity/27-03-2023?city=Dubai&country=UAE&method=16 for instance. Mon 7:01 27/3/23
A
3
This is not the case - see https://api.aladhan.com/v1/timingsByCity/27-03-2023?city=Dubai&country=UAE&method=16 for instance. Mon 7:01 27/3/23
A
2
No, that's just an ordered list. Actual method ids can be seen at https://api.aladhan.com/methods. Sun 4:00 18/10/20
A
1
@matovsky This is the timezone, and it differs based on the location you query for. It's actually needed because countries that implement Daylight Savings Time often change the name of the 'time' they use, and the results just start skipping or adding an hour, and that leads to a lot of confusion. You have a few options to deal with this: 1. The timings are always in military time, so just use the first 5 characters and strip out the rest. 2. Use the ISO 8601 date format returned by the API and create a date object out of it - then you can do with the display as you wish, on the client side or server side (if you're using the API server side). Just append `&iso8601=true` to your query parameters to get the date in that format, For instance: `http://api.aladhan.com/v1/calendar?latitude=51.508515&longitude=-0.1254872&method=2&month=4&year=2017&adjustment=1&iso8601=true`. Hope this helps. Wed 9:16 9/9/20
A
2
Please share the actual query. Obviously no city or country is a bad request. Sun 9:34 26/4/20