Using REST API's by Glenn Inn
You may have written a cool application, Cool App, that needs to do BlueJeans-y things on behalf of its users. Put another way, your application wants to be a BlueJeans concierge for its users.
This step by step guide will provide you with an example of how to create Client authentication keys and use the onVideo REST API's authenticate and receive an access token.
Step 1
From your BlueJeans Administrator
The first step to enabling your Cool App to call BlueJeans API's is for it to Authenticate. BlueJeans refers to this type of authentication as client authentication.
Client Authentication requires two unique strings that are uniquely associated with your application. You should treat securely these strings to prevent malicious applications from gaining access to BlueJeans
Login to the BlueJeans Web Portal using an Enterprise Administrator's account. Click on the Admin link that appears on the menu running across the top of the page
From the Admin page, select the OAuth link to get to the page which manages the Authentication Keys
Click on the button Add New App to start entering information about your new Cool App
We will be entering into these BlueJeans fields the information to create OAuth Client keys for your Cool App application.
Click on the Save button when done.
The BlueJean Admin portal will have listed in its collection of OAuth applications, an entry for your Cool Application. There are two fields contained in this entry that you need to copy and forward to the Cool App adminstrator. They are:
Step 2
Create a Concerige-Session
The next step is to make the API call to authenticate with BlueJeans using the newly created client keys and create a concierge session.
When an application authenticates, the BlueJeans cloud returns something called an access token which becomes your software passkey to call API's.
BlueJeans uses the industry standard OAuth protocol for authentication.
{ "grant_type": "client_credentials", "client_id": "coolapp", "client_secret": "4cb3711286b74b43a189da95a347b6fc" }
{ "access_token": "7db847d4fcb04f79982d9fa776592a31", "expires_in": 3600, "scope": { "enterprise": 28663, "partitionName": "z2", "partition": { "id": 2, "name": "z2" } } }