Token/Authorization code length will increase
Scheduled Maintenance Report for LogMeIn GoTo APIs
Completed
The scheduled maintenance has been completed.
Posted Mar 16, 2020 - 08:00 UTC
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Mar 16, 2020 - 07:01 UTC
Scheduled
Starting on March 16th, 2020, we will change the token and authorization code format to improve the API in terms of reliability, security and speed.

Date and Time:
March 16, 2020, 07:00 AM to 08:00 AM UTC

LogMeIn is implementing JSON Web Tokens (JWTs) for authorization codes, access and refresh tokens. Authentication will be handled using the same calls and steps as before, but using JWTs. The difference for your applications is that the respective lengths of authorization codes, access and refresh tokens are much larger to 900 characters and possibly more.

If your integration places no restrictions on token or authorization code length, you do not have to change anything.

If your integration cannot accept larger values, you will need to remove restrictions on the maximum length of these values.

Please direct any questions to developer-support@logmein.com. We apologize for any inconvenience this may cause and appreciate your support.
Posted Mar 06, 2020 - 16:26 UTC
This scheduled maintenance affected: GoToMeeting API Status, GoToTraining API Status, GoToWebinar API Status, GoToAssist API Status, GoToAssist Corporate Provisioning API Status, and GoTo Developer Center Frontend Status.