GoTo Developers
API Status
GoTo Developers


The SDKs do NOT support:

  • GoToAssist Service Desk
  • GoToAssist Remote Support
  • GoToAssist Corporate
  • Admin
  • SCIM

The available SDKs are licensed under the SDK License Agreement.


All SDKs require .NET Framework 4.0 or higher and are dependent upon Json.NET by James Newton-King.


Install from the NuGet Gallery

All SDKs are available as packages on the NuGet gallery. To install them use the Package Manager Dialog(link is external) or run from the Package Manager Console(link is external):

PM> Install-Package LogMeIn.GoToMeeting.NET
PM> Install-Package LogMeIn.GoToWebinar.NET
PM> Install-Package LogMeIn.GoToTraining.NET
PM> Install-Package LogMeIn.GoToCoreLib.NET

Each of the above commands will install the respective SDK and the Json.NET dependency.

Direct download

File Description File Size Download Link MD5 Checksum
GoTo Core Library
----------------- --------- ------------- -------------
GoTo Core Library .NET SDK version 2.2.0 binaries 242 KB bef9ea129f0294bb4e574bfc7197c7b6
GoTo Core Library .NET SDK version 2.2.0 sources 15 KB 3ab9f6e518bbf1b2ed444df528788948
GoTo Core Library .NET SDK version 2.2.0 documentation 88 KB 9e07cea7df777cc4bf8178325bda1335
----------------- --------- ------------- -------------
GoToMeeting .NET SDK version 1.1.0 binaries 268 KB 57d26ba092a54b26767fd93898e18546
GoToMeeting .NET SDK version 1.1.0 sources 53 KB e2e8e7582660ec5c2a29bb6ed1612ff7
GoToMeeting .NET SDK version 1.1.0 documentation 501 KB dfc5ed979112875b8dc9c7c3cd6f3c17
----------------- --------- ------------- -------------
GoToTraining .NET SDK version 1.1.0 binaries 257 KB 12824d84f130f5bedd81fc38acb34553
GoToTraining .NET SDK version 1.1.0 sources 38 KB da4b6e83639c7d4c99c00566391143ec
GoToTraining .NET SDK version 1.1.0 documentation 283 KB 4c85d79eda9bcc1d903e2aeb208ad5b7
----------------- --------- ------------- -------------
GoToWebinar .NET SDK version 2.3.0 binaries 287 KB 0f53121115f39232462ac3f7b4b699bf
GoToWebinar .NET SDK version 2.3.0 sources 100 KB c535aa12da6e750fccb5ebc4cbe3d67e
GoToWebinar .NET SDK version 2.3.0 documentation 833 KB f77839e5167c6e5f51db7f5562c2d5c6

To use the binaries extract the respective binary archive and reference both contained DLLs from your own project.

To use the source code extract the respective source archive. The source code is distributed as a Visual Studio project which you can add to your solution (version 2010 or greater required). Once opened, please enable package restore during build by checking the box "Allow NuGet to download missing packages during build" under Tools -> Options -> NuGet Package Manager -> General, then build once so the dependency is downloaded.

Getting started

The following tips assume that you already have

  • a GoTo product account
  • a GoTo developer account
  • a client ID for the respective GoTo product. You obtain this ID after creating a client in your developer account.

If you do not, please refer to steps 1-3 of our Getting started guide.

To integrate the GoTo product into your application you need to install the homonymous SDK as well as the core library for authentication. For example, to develop for GoToWebinar, you need to install GoToWebinar.NET and GoToCoreLib.NET.

Before you make any calls you need to authenticate and obtain an access token.

OAuth Flow

The first step is to generate the authorization URL where the user's browser will be directed. For this you'll need your app's client ID and optionally the URL where the user will be redirected after the authorization to use your application:

using LogMeIn.GoToCoreLib.Api;
string clientId = "nMf9SaIASQ7Jy94Ehyq8GcyopR4MQSbp";
string clientSecret = "loHznAxTuXGfFaMQ";
var oauth2Api = new OAuth2Api(clientId, clientSecret);
string authUrl = oauth2Api.GetOAuth2AuthorisationUrl(); // => ""

Then you need to direct your user's browser to this authorization URL. The user will now login with their GoTo product account credentials and click "Approve" to allow your application access to their product data. After approval, the user will be redirected and you need to capture this redirection URL in order to extract from it the OAuth flow response key. You will use the latter to obtain your access token, for example:

/* using a WinForms WebBrowser implementation */
void webBrowser_Navigated(object sender, WebBrowserNavigatedEventArgs e)
    string responseKey = oauth2Api.GetResponseKey(e.Url); // => "a2647d1379894cc2001eb31689cacccc"
    var tokenResponse = oauth2Api.GetAccessTokenResponse(responseKey);
    var accessToken = tokenResponse.access_token; // => "RlUe11faKeyCWxZToK3nk0uTKAL"

Direct Login (Deprecated)

This authentication API is now deprecated. All new clients will not be able to use this API. If you have a client for which the direct login works, that will continue to work for now.

using LogMeIn.GoToCoreLib.Api;
string userName = "";
string userPassword = "abcxyz";
string clientId = "nMf9SaIASQ7Jy94Ehyq8GcyopR4MQSbp";
string clientSecret = "loHznAxTuXGfFaMQ";
var authApi = new OAuth2Api(clientId, clientSecret);
var tokenResponse = authApi.directLogin(userName, userPassword);
var accessToken = tokenResponse.access_token; // => "RlUe11faKeyCWxZToK3nk0uTKAL"

Token Refresh

When you get an access token, the response also includes a refresh token. At the end of your access token's lifetime, you can send the refresh token in a call to obtain a new access token and refresh token pair:

var refreshToken = tokenResponse.refresh_token; // => "d1cp20yB3hrFAKeTokenTr49EZ34kTvNK"
tokenResponse = authApi.GetAccessTokenUsingRefreshToken(refreshToken)

Further calls

Once you have obtained your access token you can perform any other call passing in the access token as a parameter. For example, to list the starting times of all scheduled meetings:

using LogMeIn.GoToMeeting.Api;
var meetingsApi = new MeetingsApi();
var meetings = meetingsApi.getUpcomingMeetings(accessToken);
meetings.ForEach(m => Trace.WriteLine(m.startTime));