Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timestamp mismatch #7

Open
matthewberryman opened this issue Jun 28, 2017 · 2 comments
Open

Timestamp mismatch #7

matthewberryman opened this issue Jun 28, 2017 · 2 comments
Assignees
Labels

Comments

@matthewberryman
Copy link
Contributor

You specify start and end times with a timezone offset but the API expects Zulu (UTC)
{"statusCode":400,"error":"Bad Request","message":"child "start" fails because ["start" must be a string with one of the following formats [YYYY-MM-DDTHH:mm:ssZ]]","validation":{"source":"query","keys":["start"]}}

@tomasholderness
Copy link
Contributor

Hi @matthewberryman, the API expects an UTC offset in the form of "+0700" or "-0500". Confusingly the short hand for this in moment.js date formatting is "Z" for "zulu offset" not "zulu time".

For example a start time of "2017-02-21T07:10:00+0700" would return all reports that occurred after 07:10 AM at UTC+0700 (Indonesia).

@matthewberryman
Copy link
Contributor Author

Should it work for offsets too? It's not working for me at +1100. Given we may want to roll this out for other regions I don't think we should be specific to -0500 or +0700.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants