Comments for API UX

Comment on The 5 laws of API dates and times by The 5 laws of API dates and times | Topic | Sc...

The 5 laws of API dates and times | Topic | Sc... — Mon, 13 Jun 2016 09:00:46 +0000

[…] Let's say you're building your first API. Be it public, private, or some hybrid thereof, don't be surprised if your first defect is date/time-related. Do not underestimate how much trouble you can … […]

Comment on URL Design for RESTful Web Services by URL Design for RESTful Web Services | AddThis Blog

URL Design for RESTful Web Services | AddThis Blog — Tue, 24 May 2016 12:38:58 +0000

[…] Engineering, Charlie Reverte, posted today at APIUX.com. To read the rest of the blog post, click here to go over to their […]

Comment on The 5 laws of API dates and times by Writing OpenAPI (Swagger) Specification Tutorial – Part 4 – Advanced Data Modeling | API Handyman

Sun, 17 Apr 2016 15:52:44 +0000

[…] should read the 5 laws of API dates and times by Jason Harmon to learn how to handle date and time with an […]

Comment on Authentication: Don’t be Clever by Dave

Dave — Mon, 21 Dec 2015 03:55:47 +0000

Not sure where things with OAuth 2 stand today, but I do know that the lead author resigned while writing the spec because he thought the whole thing was a big failure.

http://hueniverse.com/2012/07/26/oauth-2-0-and-the-road-to-hell

Something to think about.

Comment on The 5 laws of API dates and times by Stephan Smith

Stephan Smith — Sat, 12 Dec 2015 00:04:00 +0000

Great article. I am using moment.js and found the following helped solidify how to accept any TZ, store in UTC and return UTC.

/* 1. Gets the local date time in ISO-8601 format. ex: “2015-12-11T18:52:59-05:00” */
var localDateTime = moment().format();

/* 2. POST to the API Body: { date: “2015-12-11T18:52:59-05:00” } */

/* 3. On Server convert the localtime to UTC: “2015-12-11T23:52:59+00:00” */
var UTCTime = moment.utc(req.body.date).format();

/* 4. Store the UTCTime in the DB. */

/* 5. Returned to the user in an JSON */
/* res.json( { date: “2015-12-11T23:52:59+00:00” } ); */

/* 6. Testing in the Browser: */
var localDateTime2 = moment(“2015-12-11T23:52:59+00:00”).format();

/* Assert we got a UTC that converts back into a local time we originally sent. */
localTime == localTime2

This should be to specific moment commands for local and server side dates.

Anyone?

Comment on How OAuth 2 trumps Basic authentication by zonbii

zonbii — Thu, 29 Oct 2015 17:48:50 +0000

SSL + Basic Auth if using server cert pinning or a 3rd party signed cert shouldn’t be an issue. Is only when you pass the exchange self signed public key in the open that contain the risk.

Comment on The 5 laws of API dates and times by Build a Better API | Mahmoud Zalt (BLOG)

Build a Better API | Mahmoud Zalt (BLOG) — Tue, 11 Aug 2015 16:43:24 +0000

[…] http://restcookbook.com/Basics/caching/ /2013/03/20/5-laws-api-dates-and-times/ Don't forget to share it. Posted in API, […]

Comment on API Hierarchy of Needs by Applying Psychology to APIs: the Best of API Hierarchies of Needs

Applying Psychology to APIs: the Best of API Hierarchies of Needs — Fri, 31 Jul 2015 13:52:38 +0000

[…] Read the article here. […]

Comment on An Overview of REST Metadata Formats by Gavin Engel

Gavin Engel — Thu, 23 Apr 2015 22:18:06 +0000

Where do we stand in 2015?

Comment on How to localize your API by Jason Harmon

Jason Harmon — Wed, 03 Dec 2014 15:35:49 +0000

In reply to Budy. ISO8601 specifies Gregorian calendar only. Past that, determining the local timezone is the UX's responsibility. This can be quite complicated in mobile scenarios, so the API should stick to UTC in the response. See my article 5 Laws of API Dates and Times for more info.