GoTo Developer Center Changelog
Super admin are no longer required to be associated to all phone numbers (DID) of an organization (pbx) to send/receive messages from the messaging API
. They can act on the behalf of another user that has the permission to do such actions.
New notifications are available on the ringing action in the Web Calls API
Version 2.1.2 adds a redirect URI parameter to the OAuth2Api.getAccessTokenResponse method. This parameter is required for clients with more than one redirect URI.
Recording URLs can now be returned in the recording search assets responses. Have a look at the updated doc here
The new GoToConnect web calls API is available! The documentation is available here
The Admin API documentation is now representing the whole set of path that are available for developers. This updated version can be consulted here
The developer portal now offers Postman collections for download directly from each API. Each API has its Postman collection available for download in the top right of its respective API page. For more information about using Postman, consult the How to use Postman API collections
The GoToWebinar SDK 2.5.0 version is avilable. You can find the new version in the Java
The line Realtime events are no longer supported. Please use the line.v2 events
The GoToMeeting SDK does now support .Net Standard 2.0. You can find the new version in the SDK guide
In the Users API
, userKey should be used instead of the user email. The userKey matches the one from the Admin API
. The email is deprecated.
For API requests with required date/time values as parameters, we do now always return an error 400 if the supplied values are invalid (was 400, 404, or 500 before).
If the email for the API request Get organizer by email is invalid we do now return an error 400 (was 500 before).
In the realtime API
, there is now a limit on how many active sessions can be alive per user (active session here means an open session with an active websocket connection). This limit for a single user is 30, after which we respond with 400 Bad Request.
When a limit is reached on the GoToConnect Messaging API
, a Retry-After header is returned with the value to wait in seconds before retrying.
The documentation of the GoToConnect Call Reports API
was updated. The API will return a http status of 429 if too much requests are done from a client.