How to Integrate Bolt.new with GoToWebinar

GoToWebinar uses the GoTo developer platform for all API access. Go to developer.goto.com and sign in with your GoToWebinar account credentials. Click 'Add App' to create a new developer application. Give it a name like 'Webinar Manager' and select 'GoToWebinar' as the product. Under 'OAuth Settings', set the authorization type to 'Authorization Code'. You need to add a redirect URI — this is the URL where GoToWebinar sends the authorization code after the user approves access. Enter your deployed URL here (e.g., https://your-app.netlify.app/api/gotowebinar/callback). You cannot use localhost or WebContainer URLs for OAuth — GoToWebinar validates that the redirect URI matches exactly what's registered. After creating the app, copy your Client ID and Client Secret. These are your OAuth credentials. The Client Secret is sensitive — store it server-side only. Also note that GoToWebinar organizer keys (accountKey) are returned as part of the OAuth token response and identify which organizer's webinars you're managing. Scope your access by requesting 'collab:webinar:create collab:webinar:read' in your authorization URL.

GoToWebinar uses OAuth 2.0 authorization code flow, which has two steps: redirecting the user to GoToWebinar's authorization page, then exchanging the returned authorization code for access and refresh tokens. Create two API routes: one that generates the authorization URL and redirects the user, and one that handles the callback and exchanges the code for tokens. The access token expires in 3,600 seconds (1 hour). Store both the access token and refresh token in your database alongside their expiry time. Build a token refresh helper that checks if the current access token is expired and automatically requests a new one using the refresh token before making API calls. This refresh logic is critical — without it, your integration will break every hour and require users to re-authorize. The entire OAuth flow must happen from your deployed site since Bolt's WebContainer has no stable URL that GoToWebinar can redirect back to. During development, you can hardcode a test access token to test other API functionality without going through the OAuth flow.

1// lib/gotowebinar-auth.ts
2const GOTOWEBINAR_TOKEN_URL = 'https://authentication.logmeininc.com/oauth/token';
3
4export async function exchangeCodeForTokens(code: string) {
5  const credentials = Buffer.from(
6    `${process.env.GOTOWEBINAR_CLIENT_ID}:${process.env.GOTOWEBINAR_CLIENT_SECRET}`
7  ).toString('base64');
8
9  const response = await fetch(GOTOWEBINAR_TOKEN_URL, {
10    method: 'POST',
11    headers: {
12      Authorization: `Basic ${credentials}`,
13      'Content-Type': 'application/x-www-form-urlencoded',
14    },
15    body: new URLSearchParams({
16      grant_type: 'authorization_code',
17      code,
18      redirect_uri: process.env.GOTOWEBINAR_REDIRECT_URI!,
19    }),
20  });
21
22  if (!response.ok) {
23    throw new Error(`Token exchange failed: ${await response.text()}`);
24  }
25
26  const tokens = await response.json();
27  return {
28    accessToken: tokens.access_token as string,
29    refreshToken: tokens.refresh_token as string,
30    expiresAt: Date.now() + tokens.expires_in * 1000,
31    organizerKey: tokens.organizer_key as string,
32    accountKey: tokens.account_key as string,
33  };
34}
35
36export async function refreshAccessToken(refreshToken: string) {
37  const credentials = Buffer.from(
38    `${process.env.GOTOWEBINAR_CLIENT_ID}:${process.env.GOTOWEBINAR_CLIENT_SECRET}`
39  ).toString('base64');
40
41  const response = await fetch(GOTOWEBINAR_TOKEN_URL, {
42    method: 'POST',
43    headers: {
44      Authorization: `Basic ${credentials}`,
45      'Content-Type': 'application/x-www-form-urlencoded',
46    },
47    body: new URLSearchParams({
48      grant_type: 'refresh_token',
49      refresh_token: refreshToken,
50    }),
51  });
52
53  const tokens = await response.json();
54  return {
55    accessToken: tokens.access_token as string,
56    expiresAt: Date.now() + tokens.expires_in * 1000,
57  };
58}

With valid OAuth tokens, you can call GoToWebinar's REST API to create webinars, list upcoming sessions, and manage registrants. GoToWebinar's API base URL is https://api.getgo.com/G2W/rest/v2/organizers/{organizerKey}/. All requests require the Authorization: Bearer {accessToken} header. Creating a webinar requires specifying the subject (title), description, times (startTime and endTime in ISO 8601 format), and whether it's a single session or series. GoToWebinar returns a webinarKey that uniquely identifies the webinar — save this key for subsequent operations like adding registrants or fetching attendees. Registration management uses the webinarKey to list registrants, add new registrants with their contact details, and retrieve individual join links. GoToWebinar automatically generates confirmation emails with join links when you create a registrant via the API. Rate limit of 100 requests per minute applies per access token — cache registrant lists that change infrequently to stay under the limit.

1// app/api/gotowebinar/webinars/route.ts
2import { NextResponse } from 'next/server';
3
4const G2W_BASE = 'https://api.getgo.com/G2W/rest/v2';
5
6export async function GET() {
7  const accessToken = process.env.GOTOWEBINAR_ACCESS_TOKEN; // Replace with DB lookup
8  const organizerKey = process.env.GOTOWEBINAR_ORGANIZER_KEY;
9
10  const fromDate = new Date().toISOString();
11  const toDate = new Date(Date.now() + 90 * 24 * 60 * 60 * 1000).toISOString();
12
13  try {
14    const response = await fetch(
15      `${G2W_BASE}/organizers/${organizerKey}/webinars?fromTime=${fromDate}&toTime=${toDate}`,
16      {
17        headers: {
18          Authorization: `Bearer ${accessToken}`,
19          Accept: 'application/json',
20        },
21      }
22    );
23
24    const data = await response.json();
25    return NextResponse.json(data);
26  } catch (error: unknown) {
27    const e = error as { message: string };
28    return NextResponse.json({ error: e.message }, { status: 500 });
29  }
30}
31
32export async function POST(request: Request) {
33  const accessToken = process.env.GOTOWEBINAR_ACCESS_TOKEN;
34  const organizerKey = process.env.GOTOWEBINAR_ORGANIZER_KEY;
35  const { subject, description, startTime, endTime } = await request.json();
36
37  const response = await fetch(
38    `${G2W_BASE}/organizers/${organizerKey}/webinars`,
39    {
40      method: 'POST',
41      headers: {
42        Authorization: `Bearer ${accessToken}`,
43        'Content-Type': 'application/json',
44      },
45      body: JSON.stringify({
46        subject,
47        description,
48        times: [{ startTime, endTime }],
49        type: 'single_session',
50        isOnDemand: false,
51      }),
52    }
53  );
54
55  const data = await response.json();
56  return NextResponse.json(data, { status: response.ok ? 201 : 400 });
57}

With the API routes in place, build a management dashboard that gives your team full visibility into upcoming webinars and registrant data. A well-designed webinar dashboard shows three views: upcoming webinars (list of scheduled sessions with registration counts and quick actions), registrant management (expandable view of who has registered for each webinar with their name, email, and registration date), and past webinar analytics (attendance rate, poll results, and recording links). The dashboard is primarily read-only with create and cancel as the main write operations. Use React's useEffect to fetch data when the dashboard mounts. For the registrant view, only fetch registrant details on demand (when the user clicks 'View Registrants') to avoid hitting GoToWebinar's rate limit by loading all registrant data upfront. Show registrant counts on the webinar cards but load full lists lazily. GoToWebinar returns rich metadata about each webinar including description, estimated attendance, and whether it's a series — use this data to make the dashboard informative without additional API calls.