Take the 2-minute tour ×
Web Applications Stack Exchange is a question and answer site for power users of web applications. It's 100% free, no registration required.

What's the recommended timestamp format for a REST GET API like this:

http://api.example.com/start_date/{timestamp}

I think the actual date format should be ISO 8601 format, such as YYYY-MM-DDThh:mm:ssZ for UTC time.

Should we use the ISO 8601 version without hyphens and colons, such as:

http://api.example.com/start_date/YYYYMMDDThhmmssZ

or should we encode the ISO 8601 format, using for example base64 encoding?

share|improve this question

closed as not constructive by Alex, Barry Mar 6 '12 at 13:16

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

1  
What's the context for this? From a programming aspect (which is off topic for this site) then any format will do as long as you publish it and stick to it. The consumers of your API will be able to code to that. From a user aspect (which is also off topic for this site) having the dashes makes it more human readable, but is this a consideration? –  ChrisF Mar 6 '12 at 13:16
add comment

1 Answer

I think the "without hyphens and colons" version is better in a URL.

So the question you should ask yourself :

Is the "without hyphens and colons" version of ISO 8601 well readable by common languages intended to consum my API ?

share|improve this answer
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.