A BlueJeans meeting is a collaboration session of 2 or more participants joining a virtual meeting-room in the cloud.
The first person to join is put into a waiting-room until other participant(s) join. When the meeting starts, all participants will be connected over video & audio.
Before you start using BlueJeans APIs, you must first have a BlueJeans account enabled for API Access. Contact
BlueJeans Support for assistance.
Once you have an account, you may start writing application code to authenticate and make API calls. *Alternatively*, you can use this developer site to test the BlueJeans APIs and develop a level of familiarity before you write production code.
To Make API Calls from This Site
If you want to use this developer site to try various BlueJeans APIs, here are the steps required to authenticate and enable your Developer Session to place API calls.
- Choose Method for Authenticating
- Click on the desired Authentication method from below.
- Click on the **Try It Out** button.
- Make Authentication request
- Follow APIs instructions and input the API parameters.
- Click on the blue **Execute** button.
- If successful, the API returns with JSON data containing a field called **access_token**. Copy/save this value.
- Authorize BlueJeans Developer Session.
- Click on the green **Authorize button**.
- The site will show you a pop-up window for authorization.
- Enter your access token in the field named **api_key**
- Click on the **Authorize** button
Your current BlueJeans developer session is now authenticated and ready to place API calls. The web site will
automatically include your access token on any API calls you make.
All API transactions (excluding Authentication) require an access token per **OAuth standards**. BlueJeans provides multiple methods for obtaining an access token. Additionally there are diffferent scopes of token access.
Grant Types
Bluejeans provides 4 different methods for users to Authenticate. Successful authentication allows BlueJeans to grant an access token to perform API operations.
- Password Credentials Grant – Authenticate with a username and password and receive an access token with user level permission. Known as two-legged OAuth.
- Meeting Credentials Grant – Authenticate with a meeting ID and meeting passcode and receive an access token with meeting level permission. Known as two-legged OAuth.
- Client Credentials Grant – Authenticate with a client ID and client secret and receive an access token with enterprise level permission. Known as two-legged OAuth.
- Authorization Code Grant – Authentication for your developer's application occurs through a redirection to a BlueJeans authentication page. The application receives an authorization code to be submitted, along with other tokens, to receive an access token. Known as three-legged OAuth. For more information please refer to the [OAuth specification](https://oauth.net/).
Access & Permissions
BlueJeans defines 3 levels of API access into the system. When an access token is granted, it carries one of these 3 levels. The scope of system functionality depends upon the token's access level.
- Meeting-level – Scope of APIs is limited to individual meetings.
- User-level – Scope depends on the requested permissions.
- App-level – provisioned either by BlueJeans personnel, or the BlueJeans Enterprise Admin, an app, is issued a client key and secret key. These tokens then are used by the BlueJeans Authentication API to receive the token. The token's scope provides access to the entire enterprise and all of its users.
All endpoints in this document that require **Enterprise Admin** access will be marked as such.
