OAuth uses different timestamp to other API functions

Question

question

chrispetchey asked Jan 29, '24 chrispetchey commented Jan 30, '24

I've found that OAuth returns access token and refresh token expiry dates as unix timestamps but in seconds where as other apis use milliseconds

For example, my call to refresh token returns me "access_token_expiration":1706549066 (10 digits)

where as a POST call to /v1/customers gives me

"created" : 1706547596608, (13 digits)

REST API

10 |2000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 1 · 2024-01-29T18:43:53Z

bryanvargas answered Jan 29, '24 chrispetchey commented Jan 30, '24

Yes that is correct. Not sure what your questions is.

1

10 |2000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

chrispetchey commented · Jan 30 at 09:06 AM

Just that it caused me some headaches when my json unixtime converter was rejecting what was supposed to be a unixdatetimestamp

0 ·