A few days ago the winding down of the 7x service was announced - https://mamluk.net/journal/winding-down-7x/.
The AlAdhan API uses several of these APIs in the background to compute timezones, distances and to geocode location strings in realtime. This means the following for the AlAdhan API:
- All endpoints of the AlAdhan API will continue to work as usual. We will internally shuffle any functonality around the timezone and distance calculations, so users will see no impact.
- From August 20 onwards, the API will simply ignore the
x7xapikey parameter and it will be removed from the documentation.
- From August 20 onwards, all endpoints that use geocoding (for which the x7xapikey was optional) like timingsByAddress, timingsByCity, calendarByAddress, calendarByCity, etc. will simply return the response with the co-ordinates masked, as if a x7xapikey was never presented (which is the majority of the API usage tody anyway).
If you are someone who uses the x7xapikey today to get the actual coordinates for those responses, please respond to this post so we can discuss how to enable you with disrupting your application(s).
Premium Hosting customers can ask for these coordinates to be enabled by raising a support ticket at https://community.islamic.network/tickets.
Finally, please note that if you run your own version of the AlAdhan API with a 7x API key (from when the source code was available on GitHub, your API will stop working on September 1 for the endpoints listed above).
Thank you.
