GoTo Developer Center Changelog
Adding a new Role Sets API
. This API allows integrators to manage account roles and set permissions for any given role.
You can now send a fax via an API, look at the documentation here
You can now get an extension number here
You can now create a new extension number here
You can now update the eventTypes on the messaging subscriptions. See the documentation here
Leg IDs are now available on voicemail events. See the documentation here
You can now add permissions for an user in a phone number, like enable SMS. See the documentation here
You can now update callerIdName information on a phone number. See the documentation here
You can now update routeTo information on a phone number. See the documentation here
The GoToMeeting requests Get meeting, Get upcoming meetings, Get upcoming meetings by organizer and Get upcoming meetings by group do now include the joinURL in the meeting object response. This URL can be used by participants to join the meeting.
Adding a new Presence API
. This API allows applications to get/set user presence, do not disturb state and receive notifications about it.
Adding a new Call History API
. This API allows applications to get the user call history.
Adding a new Voice Admin API
. This API allows applications to access phone numbers within an account (Organization).
Adding a new Voicemail API
. This API enables management and retrieval of voicemails, voicemail boxes, transcripts, and voicemail notifications.
GoToMeeting API now supports getting the profile meeting (aka Personal Meeting Room) for a given user Meeting Rooms API
The GoToWebinar SDK 2.9.0 version is available. You can find the new version in the Java
You can now get your faxes with the new Fax API. You can also get notified when a new fax is received. Have a look at the documentation here
Admin can now search across completed recording asserts of users they manage. See the specification change here
You can now get all the recording assets associated with online recordings of a webinar. See the change here
Clients can secure their webhook endpoints by validating the authenticity of requests received via the newly supported notification signature protocol described here
You can now pause/unpause recordings with the new call control API. The documentation can be read here
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 available. 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.