cancel
Showing results for 
Search instead for 
Did you mean: 
New Contributor

GoToWebinar API Support

Hi,

 

It seems that the Access Token that's returned by the GoToWebinar API has increased from 28 chars to  909 chars sometime around 1AM PDT. It caused our systems to error out as it overflowed the database colum.

 

I have expanded the column in our database and it's now working again but why the sudden change? Do you really need an Access Token to be that long, especially one that expires within an hour? Ironically enough the Refresh Token that's valid for a month is still 32 chars.

 

Thanks.

1 ACCEPTED SOLUTION

Accepted Solutions
LogMeIn Manager

Re: GoToWebinar API Support

Hi @ltctech 

 

For help with our API please reference this Help FAQ: https://developer.goto.com/support 

 

We do not provide support for the API here in the community.

 

Thanks!

 

 

Glenn is a member of the LogMeIn Community Care Team.

Was your question answered? Please mark it as an Accepted Solution.
Was a post helpful or informative? Give it a Kudo!

View solution in original post

6 REPLIES 6
LogMeIn Manager

Re: GoToWebinar API Support

Hi @ltctech 

 

For help with our API please reference this Help FAQ: https://developer.goto.com/support 

 

We do not provide support for the API here in the community.

 

Thanks!

 

 

Glenn is a member of the LogMeIn Community Care Team.

Was your question answered? Please mark it as an Accepted Solution.
Was a post helpful or informative? Give it a Kudo!

View solution in original post

New Contributor

Problem in refresh token

Hi,

 

I am facing a problem in refresh token.

I logged out from my main account and I was unable to use to the refresh token it was only 2 days.

I checked your document in https://goto-developer.logmeininc.com/how-get-access-token-and-organizer-key


I checked the response data in the above URL it said this “Refresh token identifier, valid for 30 days, or until product logout”.

 

Does this mean I need generate new response_key from OAuth2 using web browser.

Tags (1)
New Contributor

GoTo Webinar Create Registrant issue

In the last few days I noticed that when I use the Create Registrant API command the API return me the follow message

{
    "asset"true,
    "status""APPROVED"
}
 
and not
 

{

"registrantKey": 0,

"joinUrl": "https://......"

}

To retrieve the registrantKey and the joinUrl I need to retrieve all the registrants present in the webinar with Get Registrants command.

 

Is this a temporary issue or the developer team changed the Create Registrant API reponse ?

 

 

New Contributor

How to fetch the recording asset key of a simulive webinar session?

Earlier Get Webinar API was providing a recordingAssetKey for each SIMULIVE webinar in response. Now, after the new API updates, the response doesn't have recordingAssetKey

Is there any way, other than Get Recording Assets  API, which provides associated reecordingAssetKey of SIMULIVE event?

LogMeIn Contributor

Re: How to fetch the recording asset key of a simulive webinar session?

@be-pgaurav9  All developer support requests must use the template located on the developer site you referenced:  https://developer.goto.com/support

 

Thank you.

New Contributor

Gotowebinar webhook creation 400 bad request Invalid callbackUrl

I'm trying to create a GotoWebinar webhook but I'm getting 400 bad requests each time

this is my callBackUrl function

Route::get('g2w/webhook', function(Request $request) {
return response()->json([
'success'=>true
],200);
});
this is my post webhook creation request to https://api.getgo.com/G2W/rest/v2/webhooks

[
{
"callbackUrl":"https://website.com/g2w/webhook/",
"eventName":"webinar.created",
"eventVersion":"1.0.0",
"product":"g2w"
}
]
and always I get this error

{
"timestamp": 1609341614915,
"status": 400,
"error": "Bad Request",
"exception": "com.logmein.webhooks.exceptions.InvalidRequestException",
"message": "Invalid callbackUrl. callbackUrl not returning 200 OK as response. Please retry after sometime",
"path": "/v1/webhooks"
}

GotoWebinar webhooks documentation

Thanks for helping