Posted on 01-08-2014
The Dwolla API sent out an email to developers today, letting us know that, "Effective January 21, 2014, all timestamps returned by REST API endpoints will be in UTC format.” Dwolla is looking to fix the issue of ambiguous timestamps, where the time zone is variable and not indicated in the timestamp.
Currently the timestamps look like: 9/20/2013 12:45:07 AM
After the switch to UTC they will look like: 2010-11-12T13:14:15Z
Formatted according to the ISO 8601 standard. This is a much cleaner, internationalized approach. I’ve seen this mistake a lot, and still do it myself on some new systems. As an self-centered american, we tend to think the world evolves around us, and we don’t think about these scaling issues ahead of time.
Are your API data formats in UTC? No? Maybe it is something you want to change before you grow too big and get too many developers on your API.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Hello World Product API With Blueprint, RAML And Swagger
- The New Github Developer Program and Integrations Page
- I Have A Valuable API Resource, What Now?
- A Better Understanding Of Government APIs And Their Consumers Before Considering Charging For Use
- So You Wanna Do a Spreadsheet or Database To API Startup
- Jumpstarting the Automobile API Conversation With Carvoyant
- Some Of The Common Building Blocks of Payment APIs
- API Badging and Credentialing To Demonstrate Skills
- Finding Good API Developer Talent Is Hard
- Common Building Blocks Of API Design