- Account assistants
- Account Information
- Affiliate Program
- Audio & Video
- Branding / Custom / Whitelabel
- Branding Tool
- Break-out Rooms
- Call to Action
- Capacity & Limits
- Creating & managing sub-accounts
- Decisions - Professional Voting
- Event tokens
- Evergreen webinars
- How to join meeting on mobiles
- Hubspot Integration
- Language interpretation
- Meetings & Webinars
- Pabbly Connect
- Paid Webinars
- Presence Controller
- Presence manager
- Room Chat
- Screen Sharing
- Session Management
- Tests & Surveys
- Virtual Backgrounds
- Vote manager
- Waiting rooms
- Webinar and Meeting Room Features
- Statistics & reports
- Website Presenter
- Wordpress plugin
How to use LiveWebinar API?
LiveWebinar API allows you to perform all the operations that are possible with your web client in the account panel or within your account mobile app.
1. In order to use the following authorization flow (OAuth2 Authorization flow) you will need to register your app in our API to get your App Client ID, Client Secret and Redirect URL.
Head to https://app.livewebinar.com/api-apps to create APP credentials.
Use OAuth2 authorization for web application integration or use JWT for Server-to-Server integration.
More details at https://docs.archiebot.com
|curl --location --request POST
--header 'Accept: application/vnd.archiebot.v1+json' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'name=WishList WP Plugin' \
|Status: 201 Created
"name": "WishList WP Plugin",
POSSIBLE RESPONSE CODES
|500 Internal Server Error
500 3rd party client already exists.
2. Navigate user to the authorization page (open a popup or redirect them to this page):
|redirect_uri||=||an HTTPS URL where we have to redirect user when
|response_type||=||as you will be replacing the code, you will get with user’s
API access token
To set-up this integration on our end, we need to get the redirect URL on your side so we know where to redirect the user back when the integration is authorized on our end.
2. Once the user confirms the authorization, we will redirect them back to the redirect url URL with parameters: code and state (with your value if passed). Param code is your API
authorization code for this user.
3. Exchange authorization code to access_token and refresh_token (real authorization).
application/vnd.archiebot.v1+json with parameters:
|code:||abc123 (this is the code you got with step 2 above)|
|redirect_uri:||the same redirect URI as passed when getting the code we
also need it to finish setting you up. i.e:
You will get user’s access_token and refresh_token for the API. Store it on your side and use it for further API requests for this user.
expires_id determines the expiration of access_token.
When expired or request unauthorised use refresh_token.
To get new tokens please go to:
|Required API header:||Link|
|Authorize by authorization code:||Link|
4. From now on you have on your side access_token and refresh_token for this user to LiveWebinar API.
YourWebsite API OAuth Credentials:
1. Update your account settings (user_id parameters you get from the test endpoint)
Update account details:
Let us know if you want to send specific details and we’ll respond with the actual API query.
Important: we don’t allow turning off email notifications over to API yet. This has to be done in the user account panel (you have to go to the “Advanced” tab when you schedule the meeting).
Please let us know in case you want us to add this (this will simplify the process).
2. Create Webinar/Meeting Room (in our API we call them widgets):
Such a request will create a webinar room (in API called ‘widget’) which will not ask participants for anything besides nickname on entrance. If you want to display a web form and gather some information you want to pass the form parameter with the webinar creation request.
https://yourwebsite.com/room/123-123-123 (or anything you like) instead of https://livewebinar.com/123-123-123
Simply create a blank HTML page, put the code in it and fill in the options:
• _license_key - required, it is a widget->token you get after creating webinar room. i.e.: 123-123-123
• Optionally if you want to differentiate participants by role, you can add option _role_token which should have a string value of role hash (part of widget objects you get after creating webinar/widget). This way, if you know you’re displaying a page for your user, you can set him up automatically with a hosting role.
Note: for host we issue a URL to the meeting that holds that role automatically so in the calendar he has i.e. https://yourwebsite.com/room/123-123-
123/abcxyz123 where abcxyz123 is the role hash for host role. Then just check if you got this in the URI and pass that as _role_token.
• Optional _nickname - if you know the name of this participant (i.e. from logged session)
3. Add panelist to webinar
recognize this participant as a host or presenter. Below you will the option to generate direct room URLs that will also hold participant details like name, email etc.
• Option 1 (without web form before webinar):
|emails||required, a valid email of the participant|
|role||optional, default attendee role assigned values: attendee, presenter, moderator|
As a result, you will get an object where the most important are attributes personal_token and/or personal_url.
This way the system will use email and other data from this personal URL.
• Option 2:
with the web form on entry attached to the webinar during widget creation. This is the same request as for Option 1 but you also need to pass also data for the fields in that form (at least for
4. Delete webinar
You can also enable/disable the room instead of deleting it):
5. Update webinar
It’s very similar to creating webinar but PUT requests.
ROOM URL HACKS that you may consider.
|Direct URL for
role room URL -
https://app.livewebinar.com/123-123-123/x/IYuUtn2P -> role token
image hosted by
You can find the full API documentation here.