Date and time conventions
Overview of time and date conventions
GoToMeeting, GoToWebinar, GoToAssist, and GoToTraining
In all POST calls, use the UTC date format, 2015-12-11T09:00:00Z (i.e., include the trailing Z), to ensure correct creation of dates. In all cases, you should also declare the organizer's local time zone. This ensures the event displays in the organizer's time zone in the Admin Center for GoToMeeting, GoToTraining, and GoToWebinar. These practices also result in consistent and correct treatment of dates in other APIs. If you omit either or both values, inconsistent behavior for event dates and times can result.
The GoToAdmin reports use a millisecond time format. For example, at this writing, on May 12, 2020 at 11:00:54 local time, the millisecond value is 1589306454933.
Time zone reference (based on ICANN tz data) - use the tz database name for time zones in API calls.
- How much do the LogMeIn APIs cost?
- How do I get started?
- How do I get support for the APIs?
- Can I access more than one product API?
- What are the rate limits for the APIs?
- How to login or create a developer account
- How to create an OAuth client
- How to obtain an access token
- How to obtain and use refresh tokens
- How to use Postman API collections
- GoToWebinar webhooks
- How to use GoToWebinar webhooks
- How to use GoToConnect API to fetch Account Users and Lines
- Date and time conventions
- Paging, Sorting & Filtering Output
- OAuth Migration Guide
- Direct Login Migration
- Migrating from GoToConnect to LogMeIn Authentication API
- Java SDK
- .NET SDK
- SDK License Agreement