- The API endpoint is
GET [project_url]/api/timestamp/:date_string?
- A date string is valid if can be successfully parsed by
new Date(date_string)
. Note that the unix timestamp needs to be an integer (not a string) specifying milliseconds. In our test we will use date strings compliant with ISO-8601 (e.g."2016-11-20"
) because this will ensure an UTC timestamp. - If the date string is empty it should be equivalent to trigger
new Date()
, i.e. the service uses the current timestamp. - If the date string is valid the api returns a JSON having the structure
{"unix": <date.getTime()>, "utc" : <date.toUTCString()> }
e.g.{"unix": 1479663089000 ,"utc": "Sun, 20 Nov 2016 17:31:29 GMT"}
- If the date string is invalid the api returns a JSON having the structure
{"unix": null, "utc" : "Invalid Date" }
. It is what you get from the date manipulation functions used above.
- https://fobabs-timestamp-microservice-1.glitch.me/api/timestamp/2017-09-12
- https://fobabs-timestamp-microservice-1.glitch.me/api/timestamp/1505174400000
- {"unix":1505174400000,"utc":"Tue, 12 Sep 2017 00:00:00 GMT"}
- You'll need to clone this repository
$ git clone https://github.com/fobabs/timestamp-microservice.git
$ cd timestamp-microservice
- Make sure you have node 12.*.* installed. We used ES6 modules which only support version 12 and later.
- If you have the devDependency located in package.json installed globally, you can skip this step, otherwise install it using
$ npm install --only-dev
- Start up the server
$ npm start
NOTE: The server is available at http://localhost:3002
OR http://127.0.0.1:3002
.