APIv1 has been deprecated since May 25th, 2023 and is scheduled for removal on June 1st, 2024. All date-times mentioned are UTC in 24 hour format.
As we are near the sunset date, active deprecation phase begins. This issue serves as a medium of information about what's coming for APIv1.
APIv1 will go through several brownout phases. During these, APIv1 will respond with 503 Service Unavailable.
May 6th, 6:00 - 8:00
May 11th, 5:30 - 8:30
May 16th, 5:00 - 9:00
May 20th, 4:30 - 9:30
May 23rd, 6:00 - 8:00
May 23rd, 13:00 - 15:00
May 23rd, 20:00 - 22:00
May 26th, 5:00 - 10:00
May 26th, 15:00 - 20:00
May 28th, 18:00 - 00:00
May 30th, 16:00 - 00:00
Throughout May 31st, during odd hours until 20:00 (1:00, 3:00, 5:00, 7:00, 9:00, 11:00, 13:00, 15:00, 17:00, 19:00)
On June 1st at midnight, APIv1 will cease to operate for good*. It will respond with 410 Gone, and may finally take some RESTful rest. 🕊️
*I will closely monitor the situation evolve over the course of May, and will take action in consequence June 1st regarding discontinuation of service. Depending on what I'm observing, I may grant extended support to certain agents at my sole discretion.
APIv1 has been deprecated since May 25th, 2023 and is scheduled for removal on June 1st, 2024. All date-times mentioned are UTC in 24 hour format.
As we are near the sunset date, active deprecation phase begins. This issue serves as a medium of information about what's coming for APIv1.
APIv1 will go through several brownout phases. During these, APIv1 will respond with
503 Service Unavailable
.On June 1st at midnight, APIv1 will cease to operate for good*. It will respond with
410 Gone
, and may finally take some RESTful rest. 🕊️*I will closely monitor the situation evolve over the course of May, and will take action in consequence June 1st regarding discontinuation of service. Depending on what I'm observing, I may grant extended support to certain agents at my sole discretion.