Skip to content
Amara Accessibility Media

Amara Accessibility Media

Building access to global information through subtitles, captions, and localization

  • Mission
    • Inclusion and Belonging
    • Culture and Appreciation
    • Morning Talks in the Mirror
  • Tech
    • Solutions and Tools
    • Product Features
  • Captions & Subtitles
    • Accessibility and Captioning
    • Translation and Localization
  • Amara Products
    • Amara Subtitle Editor
    • Amara Plus
    • Amara Community
    • Amara Enterprise
    • Amara On Demand
  • Amplifying Voices
  • Communication Guide
    • Inclusive Language
    • Accessibility
    • Global Accessibility
    • How we communicate with our Amara humans
    • Writing Style and Tips
    • Grammar and Spelling
  • Toggle search form

API Change: UTC Timezones for datetimes

Posted on July 24, 2015 By pcfben No Comments on API Change: UTC Timezones for datetimes

The API code switchover seems to have worked pretty well judging from the lack of any complaints.  Now it’s time to move to continuous improvement mode.

The first change we’re going to do is quite simple.  Before, when we returned datetimes we would not specify the timezone and it would be in Mountain Time (see #2267).  After the change, we will specify the timezone and use UTC for the timezone.

That change is a pretty minor one, but it gives us the opportunity to test out the new API changing technical policy.  Here’s a reminder of how it works.

  • When we deploy a change to the API, we’ll pick a future date to switch over to the new behavior.  This is going to be one month from today 8/24/2015.
  • Before the switchover date, we return an HTTP header to indicate that the API will be changing.  The name is X-API-DEPRECATED and the value is the switchover date in YYYYMMDD format.  So for this change, we will return “X-API-DEPRECATED: 20150824”
  • Clients can start using the new API before the switchover date using the X-API-FUTURE header.  The value should be the date of the API that you want to use, also in YYYYMMDD format.  If the X-API-FUTURE date is >= the switchover date then the new API code will be used.  So you can send “X-API-FUTURE: 20150824” to get the new behavior ahead of time.

 

 

Read these articles next

Development

Post navigation

Previous Post: Amara API Switchover
Next Post: Amara release notes 2015-07-28

More articles to learn from

Upcoming Amara API Changes – Summer 2019 Amara Announcements
Amara release notes 2018-04-04 Development
Amara release notes 2018-04-03 Development
Amara release notes 2018-03-20 Development
Amara release notes 2018-03-14 Development
Amara release notes 2018-03-06 Development

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Give us a follow

  • Facebook
  • Instagram
  • LinkedIn
  • Twitter
  • YouTube

Contact us at enterprise@amara.org

Powered by PressBook Grid Blogs theme