This question was
closed
by
zgreathouse for the following reason: The question is answered, right answer was accepted
API integration timezone
When retrieving a list of all payments, the docs suggest the transactions in the report will always be returned in the timezone of the requesting machine ip. Is there a way to override this to get results back in a consistent timezone, such as UTC? Use case would be my system being in AWS, where I don't know what timezone the machine(s) may be in.
There may be a mistake in the docs. Can you please provide a link to the doc you found which suggest the time is converted automatically?
It was here that I saw it. While it did talk about the web dashboard specifically, I guess it confused me into thinking the api was trying to get fancy as well. The docs aren't particuraly clear in regards to the timestamps/timezone/etc.
Thank you for your feedback. We'll try to make this more clear in the documentation.
When you hit the endpoint:
GET /v3/merchants/{mId}/payments - in the response body you will see that all time related fields on each payment object (createdTime, clientCreatedTime, modifiedTime...etc) are saved as a Unix Time Stamp which can be converted.
Apps, such as the Merchant Dashboard and Clover's Transactions app, convert the time stamp to local time. To be clear any conversion must be explicitly done by your app.
Example Payment Object:
Apps, such as the Merchant Dashboard and Clover's Transactions app, convert the time stamp to local time. To be clear any conversion must be explicitly done by your app.
Example Payment Object:
{
"id": "*************",
"order": {
"id": "*************"
},
"device": {
"id": "********-****-****-****-************"
},
"tender": {
"href": "https://sandbox.dev.clover.com/v3/merchants/*************/tenders/*************",
"id": "*************"
},
"amount": 2832,
"taxAmount": 234,
"cashbackAmount": 0,
"employee": {
"id": "*************"
},
"createdTime": 1547071649000,
"clientCreatedTime": 1547071649000,
"modifiedTime": 1547071651000,
"offline": false,
"result": "SUCCESS"
Those were the timestamps I had been using, really the concern was that the timezone would somehow get manipulated by the requesting IP. Thank you for confirming that is not the case and I had just misunderstood. Knowing that for certain now, converting it to the correct timezone is an easy step to finish up this integration.
Welcome to the
Clover Developer Community
1 Person is following this question.
