Normal

small_olivier.png

thumbnail_olivier.png

olivier.png

Olivier Lando

No-code

no code

We've just released a brand new [api.video plugin](https://bubble.io/plugin/apivideo-1632390165248x133502315345739780) on the Bubble.io marketplace. This plugin allows you to use the main features of api.video in your web application (video upload / video player / API calls) without having to write a single line of code.

For those who do not know Bubble.io yet, it is a no-code tool that allows you to build SaaS platforms, marketplaces and CRMs without code.

In this tutorial, we will show you the main features of the api.video plugin, taking as an example the creation of a video sharing site (similar to YouTube, but much... much more rudimentary). This will allow us to discover some of the features offered by our Bubble.io plugin, namely:

* the video uploader element
* the video player element
* the API calls

The result can be seen here: [Bubble demo application](https://api-video-tube.bubbleapps.io/version-test/).

The purpose of this article isn't to describe the api.video plugin in detail, but you can find the full documentation here: [Bubble.io plugin documentation](https://docs.api.video/docs/bubbleio-plugin).

## The demo application

Our application is composed of the following pages:

* a home page (public) - the home page contains a thumbnail of each video that has been uploaded on the website
* a video page (public) - it contains a player to watch a specific video (when a user clicks on a video title on the home page, he will arrive here)
* a login / sign up page (public)
* an upload page (logged in users only) - logged in users are able to upload a new video from this page
* an account page (logged in users only) - logged in users are able to manage their videos here

## Database schema

Our Bubble database is composed of only 2 data types: `User` & `Video`. Each video is associated with a `User` entry (the person who uploaded the video).

Here are the schemas of the 2 data types:

### User



large_userschema.png

medium_userschema.png

small_userschema.png

thumbnail_userschema.png

userschema.png

large_videoschema.png

medium_videoschema.png

small_videoschema.png

thumbnail_videoschema.png

videoschema.png

**Here is what it looks like in the Bubble interface:**

large_database.png

medium_database.png

small_database.png

thumbnail_database.png

database.png

## Installation of the api.video plugin

To begin with, we need to add the api.video plugin in the Bubble.io application. You can find the details in our documentation: [api.video Bubble.io plugin](https://docs.api.video/docs/bubbleio-plugin). 

## Pages

### Login / sign up page

The login / sign up page consists of two forms: one to register and a second one to log in. By default the login form is hidden. It shows up when the "login" button is clicked. 

#### Sign up form

The sign up form is a standard form with a "Sign up" button and 3 input fields: Email, Password & Password confirmation. When the "Sign up" button is clicked, the user is registered using the standard "sign up" Bubble workflow action. 

At this time, we generate a [delegated upload token](https://api.video/blog/tutorials/delegated-uploads) from [api.video](https://api.video). This token will be used later, every time the user wants to upload a new video. 

In order to generate the token, we use the `+ Change another field` button in the Bubble action pop-up. As a source for the value, we use `Data from an external API` and select `authenticate - generate upload token`. 

medium_workflow-sign-up-upload-token.png

small_workflow-sign-up-upload-token.png

thumbnail_workflow-sign-up-upload-token.png

workflow-sign-up-upload-token.png

#### Login form

The login form consists of a "Login" button and 2 input fields: Email & Password. When the "Login" button is clicked, the user will be logged in using the *had oc* Bubble action:


small_workflow-login.png

thumbnail_workflow-login.png

workflow-login.png

### Upload page

The upload page will contain
*  two text inputs: "Title" and "Description" 
*  a "Select a video file" button that opens a pop-up to select the video file to upload 
*  a progress bar 
*  a submit button

#### The api.video uploader element

The "Select a video file" button is not a standard button but an api.video uploader element. For more details about this element you can read the documentation here: [Bubble.io uploader element
](https://docs.api.video/docs/bubbleio-uploader). The purpose of the uploader element is to offer users of your web application the ability to easily upload videos to api.video.

The element needs one setting: the delegated upload token to use. It will use the one that has been associated with the user when they signed up. To do so, in the "upload token" parameter of the element, we've entered `Current user's upload token`. We've also applied some style to the element to make it fit with the design of our site. 

#### Progress bar

To display the upload progress bar a SimpleProgressBar element is used. Its "Percentage" value is associated with the "percent" value of the video uploader element. 

#### Workflow actions

There are five workflows defined for this page:

large_workflows-upload-page.png

medium_workflows-upload-page.png

small_workflows-upload-page.png

thumbnail_workflows-upload-page.png

workflows-upload-page.png

*  When the user arrives on the page, if they are not logged in, they are redirected to the login page 
*  When the "Title" input becomes not empty and if the video uploader element's `file_selected` value is true (meaning that the user has already selected a video file), then the "Upload" button is shown.
*  Reciprocally, when the `file_selected` becomes true and if the "Title" input field isn't empty, then the "Upload" button is shown.
*  When the "Upload" button is clicked, the "upload" action of the video uploader element is triggered. Also, the form inputs are hidden and the progress bar is shown. 
*  When the "end" event of the video uploader element is triggered, a new Video element is created in the Database. The following attributes are set:
*    videoId: the value of the videoId attribute of the uploader element (this is the id of the new video that has been returned by api.video)
*    user: the current user
*    title: the value of the "Title" input field
*    description: the value of the "Description" input field

### Home page

The home page is pretty basic. It will display a preview of all the videos that have been uploaded by any user of the application. It will look like this:


large_homepage.png

medium_homepage.png

small_homepage.png

thumbnail_homepage.png

homepage.png

#### The repeating group

A [Repeating group](https://manual.bubble.io/core-resources/elements/containers#repeating-group) is used to iterate over all the Video entries stored in the database. 

The datasource query of the repeating group is simple: `Search for videos`. A "Sort by" constraint has been added on the `Created date`field with "Descending" = `false` in order to have the latest videos displayed at the top of the page. 


large_homepage-repeating-group.png

medium_homepage-repeating-group.png

small_homepage-repeating-group.png

thumbnail_homepage-repeating-group.png

homepage-repeating-group.png

#### Repeating group elements: the api.video player element

In each entry of the repeating group, an api.video videoplayer element is used to display a preview of the video. To make the player look like a preview, the following settings are applied:


large_homepage-player-settings.png

medium_homepage-player-settings.png

small_homepage-player-settings.png

thumbnail_homepage-player-settings.png

homepage-player-settings.png

*  `autoplay` is false: we don't want all the players to automatically start when the home page appears
*  `hideControls` and `hideTitle` are true: the players are very small here, we only want to see the video 

Two workflows are also used to handle the video previews. They are respectively triggered when the video player element sends mouseenter and mouseleave events. When the mouse enters the player area, the video playback is launched thanks to the play action of the player element. On the contrary, when the mouse leaves the player area, the pause action is used to stop the playback.

Under the player element, the following details of the video are displayed:

* the title
* the views
* the author's email

The title is a link that redirects the user to the video page of that video.

 

### Video page

Users land on this page after a click on a video preview from the home page. The page layout consists of a large video player, plus some details about the video:

large_video-page.png

medium_video-page.png

small_video-page.png

thumbnail_video-page.png

video-page.png

The same video player element as on the home page is used. The only difference is that when the player element triggers a first play event, a workflow action increments the `views` value of the video in the database. 


### Account page

The Account page has almost the same layout as the home page. It consists of a repeating groups iterating on videos. The main difference here is that the videos are filtered in order to only display the ones that have been uploaded by the current user. The other difference is that a "Delete" button is present next to each video. When clicked, the `delete` endpoint of the api.video API is called, and the video entry is deleted from the database:





large_delete-video.png

medium_delete-video.png

small_delete-video.png

thumbnail_delete-video.png

delete-video.png

## Conclusion 

In this step by step tutorial we have covered the process of building a video sharing application. In particular, we have looked at the following features of the api.video Bubble plugin: 

* the video uploader element
* the video player element
* the API calls

As always, we encourage you to join our [Community Forum](https://community.api.video/) and sign up to our newsletter (you will find the link below this post). 

large_bubble_plugin.png

medium_bubble_plugin.png

small_bubble_plugin.png

thumbnail_bubble_plugin.png

bubble_plugin.png

Bubble.io + api.video: build a YouTube-like site with no code

medium_screen-shot-2021-01-26-at-11-48-47-am.jpg

small_screen-shot-2021-01-26-at-11-48-47-am.jpg

thumbnail_screen-shot-2021-01-26-at-11-48-47-am.jpg

screen-shot-2021-01-26-at-11-48-47-am.jpg

Erikka Innes

Use cases

Husband and wife team Didier Duffas and Valentina Zatevalneva dreamed of building their own digital dance academy - Neva Ballet. Their goal was to make it possible for people around the world to experience the magic of dance for fitness and health. Focused on classical dance techniques and the strength and beauty of Russian ballet, the classes would be open to anyone with the desire to learn. 

small_neva-ballet-use-case.png

thumbnail_neva-ballet-use-case.png

neva-ballet-use-case.png

## The right video tool for the Job
There were just a few hurdles standing in the way of their dream. Neither one of them had built a website before and they had no previous developer experience. Additionally, for video they needed a way to create a high quality recording for playback. They wanted something simple to implement, that would be cost effective and easy to manage. They started with Wix and Zoom. Wix's easy-to-use interface made it possible for them to create their own ecommerce site and Zoom allowed them to live stream all of their classes to a small group.

There was just one problem - the live streams. While they were great for live teaching, they wanted to offer customers a **high quality playback** of each class as well as create a backup if anything happened with their Zoom recording. 

This led them to api.video. 

api.video offers high quality HLS live streams that look great in playback, customizable players, easy implementation and reasonable prices. With these three tools combined, their digital dance academy began to take shape.

## Video recording set-up

> "Our job is to provide to our customers online classes in different disciplines based on ballet and all the physical preparation of ballerinas. Valentina used to be a ballerina in the national state ballet in Russia," Didier said. 

To bring the couple's vision to life, Didier set up an ecommerce website with Wix and then turned to setting up their classes. For the video recording implementation, he set up Zoom meetings with recording enabled. Next, he created a [live stream](https://api.video/blog/no-code/start-and-record-a-live-stream-of-your-zoom-meeting) with api.video, then added it to the Zoom meeting. Any time Valentina opened Zoom to start live streaming a class, she would speak with the class, then when it was time to begin, she cut everyone's mics but her own, started her live stream with api.video, and then with Zoom. 

Didier described the typical class set up for us: "The teacher has the camera filming giving the lesson and at the same time she can see the gallery of Zoom for the images of the students. All our members are not doing live at the same time and we advise them to make live classes sometimes just to participate so we can give feedback. But we mainly use the replay and that's the reason why also we use api.video -- <ins>because we need to provide them with high quality video for the replay.</ins>" 

small_screen-shot-2021-03-25-at-1-28-56-am.png

thumbnail_screen-shot-2021-03-25-at-1-28-56-am.png

screen-shot-2021-03-25-at-1-28-56-am.png

They decided to offer the Zoom playback alongside the high-quality api.video playback. Students had access to either playback as many times as they wanted for one week after the class. 

## No code video implementation
With their implementation together, the digital dance academy [Neva Ballet](https://www.nevaballet.com/) was born. They have now been in business for one year, and they offer classes in nine different disciplines, with subscription and a la carte purchasing models available. They have multiple channels for their live streams, and they've not only made it possible for students to take classes from anywhere, but to do so affordably. A monthly subscription to classes starts at 35 euros while others charge double with lower video quality. Individual classes start at 15 euros. Another perk the couple found is that they can teach the classes from anywhere. 

They also found their no-code implementation tremendously valuable because it meant they could manage the site on their own. 

> "We never had any developer. I didn't know how to make a website one year ago. I do everything by myself...It's really cool...For us it's very important because we are autonomous and we can do things...ourselves," Didier told us. 

By not needing a developer except for some help with a menu arrangement in Wix, Didier said they are able to keep costs low, quickly respond to problems and implement improvements. 

> “It would be very complicated for us if we had to ask a web agency or web developer to work for us. Since one year I have made so many changes and we are really in A/B testing mode. I put something, I see a change, I correct it," Didier said. 

The couple hopes to grow their digital academy over time, with more classes and teachers, and they look forward to doing so with the help of api.video. 

> "api.video will help us to evolve." --Didier Duffas


To find out how you can build your own online business with video content, [contact us](https://api.video/contact) or [sign up](https://dashboard.api.video) for an account and try one of our many tutorials and demos.

Case Study: How api.video helped a couple build a digital dance academy without coding

doug.jpg

twitter-brands.svg

Doug Twitter

Doug Sillars

Zapier is a no-code platform that makes it easy to connect services together - without writing a single line of code.

We recently upgraded our [Zapier integration](https://zapier.com/apps/apivideo) to make use of our [API webhooks](https://docs.api.video/reference/post-webhooks), so that Zapier can instantly report when an event occurs at api.video.

## Our webhooks

We currently have 4 alerts from our webhooks:

* video.encoding.quality.completed: This alert fires when a video quality is ready to playback.
* live-stream.broadcast.started: Alerts you to when a live stream has begun.
* live-stream.broadcast.ended: The opposite alert - the live stream has ended.
* video.source.recorded: Similar to the first, but specifically for when a livestream recording quality is ready.


## Now available in Zapier

When the webhook alert from api.video occurs, Zapier is alerted immediately.  That's why Zapier calls these triggers "Instant triggers"- there is no polling delay to know when the Zap must begin:

large_screenshot-2021-10-21-at-20-46-46.png

medium_screenshot-2021-10-21-at-20-46-46.png

small_screenshot-2021-10-21-at-20-46-46.png

thumbnail_screenshot-2021-10-21-at-20-46-46.png

screenshot-2021-10-21-at-20-46-46.png

As shown in the above screenshot, there are currently 4 instant Zap triggers offered by api.video.

* **Live stream started**  This alert will fire whenever a livestream has started.  You can filter on the liveStreamId to create a custom integration for a specific live stream ("when stream liXXX goes live - send an alert to a Discord channel), or have it fire for all of our live streams (livestream "liYYY" is now live.  Watch it here <link>") 
* **Live stream started** this is the opposite of the first alert - so the Discord channel knows the stream has ended "sorry you missed us, tune in tomorrow".
* **Video encoded completed**  This webhook fires for each version of the video created.  Currently, api.video encodes video at 240p, 360p, 480p, 720p, 1080p and 2160p.  When you create the Zap, you choose which size you wish to be alerted on.  For example, if you only want to show a video once the quality has reached 480p, you define the Zap to trigger when the 480p version of the video is ready, and then you'll receive that alert.
* **All live events**: This webhook incorporates all 3 live stream webhook events: started, ended and video.source.recorded (at a specific resolution). This allows you to create more elaborate Zaps with various paths based on the results - while just using one webhook.

Each Zap you create with the instant triggers will create a webhook at api.video (and when you disable the Zap, the webhook will be removed).  

> Note: There is a limit of 10 webhooks per account at api.video, so there should be some consideration on how the number of "instant Zaps" will affect your webhook limits.


In the below example, we use Zapier paths and the *All Live Events* trigger to do 3 different things - depending on the event type that is reported. (Note: Zapier paths require a "professional" level Zapier account.)


We're very excited to see how instant Zaps can help our no-code developers build apps that react instantly to changes in their api.video account.

large_screenshot-2021-10-22-at-10-55-09.png

medium_screenshot-2021-10-22-at-10-55-09.png

small_screenshot-2021-10-22-at-10-55-09.png

thumbnail_screenshot-2021-10-22-at-10-55-09.png

screenshot-2021-10-22-at-10-55-09.png

These Triggers are all live at Zapier, and our [docs](https://docs.api.video/docs/zapier) are updated with more details on how to integrate each trigger and action.

medium_screen-shot-2021-01-28-at-2-13-01-pm.jpg

small_screen-shot-2021-01-28-at-2-13-01-pm.jpg

thumbnail_screen-shot-2021-01-28-at-2-13-01-pm.jpg

screen-shot-2021-01-28-at-2-13-01-pm.jpg

Updated: our Zapier integration now features instant triggers

Welcome back to our 'So Easy, It's a Zap!' series. In this installment, we'll look at a zap that lets you combine api.video with Slack messaging without writing any code. A zap is what happens when you use Zapier to combine two or more applications together. You use one application to define a trigger that will set off an action in another application or the same application. If you want more details, check out our introductory article about Zapier - ['Create Video Integrations Without Coding - So Easy It's a Zap!'](https://api.video/blog/no-code/create-video-integrations-without-coding-so-easy-it-s-a-zap). 

## Prerequisites 

You'll need a few things to successfully complete this project: 

* api.video [account](https://dashboard.api.video/register) 
* Slack account 
* Zapier account

Slack will walk you through everything and we provide links to the content you'll need to set yourself up with Slack. 


## Configure api.video as the Trigger Event 
Api.video will be the trigger event for your Zap. Each time you add a new video in api.video, it will trigger Slack to update a channel with a message notifying everyone that its available.

To get started, do the following: 

1. Sign up and log in to Zapier.
2. Navigate to [https://zapier.com/apps/apivideo/integrations/slack](https://zapier.com/apps/apivideo/integrations/slack).
3. Under Popular Ways to Connect api.video and Slack, next to Send Slack messages for new videos created on api.video, click **Try It**. 

medium_apivideo-and-slack.jpg

small_apivideo-and-slack.jpg

thumbnail_apivideo-and-slack.jpg

apivideo-and-slack.jpg

4. Under Connect Your Apps, choose your api.video account. If it's not set up, you'll need to go through a walk through to add it, or reconnect it if it expired. You can connect or reconnect by clicking on either Connect or Please reconnect it here. Then, get your api.video from your dashboard, and add it in the field for your API key when prompted with 'Allow Zapier to access your api.video Account?' Click **Yes, Continue**. 

## Configure Slack as the Action Event
Slack will be your action event. It will deliver a notification to a Slack channel you choose every time a new video is added in your api.video account. 

1. Now you need to sign in to Slack. You'll have similar choices to those you had for api.video. In this case, we don't have a Slack account connected in Zapier yet, so we'll click **Sign in to Slack**. Sign in to your workspace, and click **Continue**. You'll walk through the steps you'd use to sign in, giving permission to Zapier to connect for you. 
2. After you've connected, use the drop-down to choose a slack channel to test with.
3. Turn on your Zap so you can test it.

## Test Your Zap
To test your Zap, add a new video to the account associated with your API key. You can do so programmatically, or you can test by doing the following:

1. Open your api.video dashboard.
2. Click **Upload**. 
3. Add a video from your computer. 
4. Wait to see if Zapier senses the video was added, and then Slack will report it in the channel. You're using a polling method, so it might take a minute or two.
5. If nothing happens, then open Zapier on your Zaps page and click the drop-down arrow next to your Zap. 
6. Click **Run Zap**. It should work within a few minutes. 

You can set up other Zaps too. Check out our entire 'So Easy its a Zap!' series in the [No-code](https://api.video/blog/no-code) section of our blog. 

large_apivideo-and-slack.png

medium_apivideo-and-slack.png

small_apivideo-and-slack.png

thumbnail_apivideo-and-slack.png

apivideo-and-slack.png

Send Messages in Slack Any Time You Create a New Video

small_screen-shot-2021-03-16-at-11-00-46-pm.png

thumbnail_screen-shot-2021-03-16-at-11-00-46-pm.png

screen-shot-2021-03-16-at-11-00-46-pm.png

Erikka Innes and Doug Sillars

As COVID-19 is forcing more educators to teaching remotely, and more organisations are cancelling in-person meetings, video conferencing is becoming more important than ever.

With entire countries under lockdown or quarantine, tools like Zoom, Skype, Hangouts and others are seeing high usage. However, these tools can have high bandwidth requirements. Zoom recommends 800 KBPS up and 1 MBPS down for group conferencing

But, what about students who do not have fast internet at home? Advice like "Go to the library" just doesn't work during a pandemic. How can the video be served at a lower bitrate for these users?

broadcast a zoom meeting, live stream, record a zoom meeting, record a livestream

medium_douglivestream.png

small_douglivestream.png

thumbnail_douglivestream.png

douglivestream.png

## Live Transcoded Streams
For streamers (professors, teachers, colleagues), there are settings that will push the video to live transcoding engines. In this example, we'll use api.video to transcode the video to a lower bitrate.

## Saving Videos for Later Playback
If you are streaming the videos, wouldn't it be great to also aggregate these videos into a portal for your students to later review? Zoom allows you to record your videos, and provides you a URL, but then you have to create the portal. What if we could create the portal from the Live Stream?

## Simple Setup
As we walk through this process, you'll see that this is an easy setup that anyone can use to share their live video streams.

## Getting Started
To begin, go to api.video and create a free account. Once you sign up, you'll see a list of keys. You'll need your production key in a few steps, so make a note of it now (or leave the dashboard open so you can come back and look).

The code for this project is hosted at Glitch. All Glitch apps get a silly subdomain (in this case ["twilight-decorous-mail"](https://glitch.com/~twilight-decorous-mail)). 

### Update 2021
The code is also pn Github: https://github.com/dougsillars/watchLivestream
You can also see an updated version at: [watch.a.video/livestream](https://watch.a.video/livestream)

1. On the Glitch page, click **View Source**.
2. Click the button **Remix to Edit**. You'll have your own version (with silly name).
3. On the left menu are all the files that create the website. Click on the **.env** line (there is a key next to it). This file will open in the middle. On lines 8, and 10 are three variables: imageUrl, apiVideo and PORT. There is no value after the equals sign. For **imageUrl**, add a url pointing to your logo. For **apiVideo**, paste in the production key from when you signed in. For **PORT** enter **3000**.

That's it - you just configured your website. Now to add your content:

1. At the top, click the **sunglasses**, and open the project in a new page. You'll see a mostly empty site. We haven't configured it yet. 
2. In the url bar, after the https:-silly-.glitch.com add **/createClass** to the end and press **Enter**. You'll get a page about creating a class. 
3. On this page, you can enter your class name, and also whether you want to record all sessions for later viewing. Press **Enter**, and you'll get some more important information: your StreamKey and the URL of your site with a URL parameter afterwards. Make a note of these as you'll need them for the next set of instructions.

## Now we are ready to stream with OBS!!
OBS is a free application available on Mac/Windows/Linux. 

1. Download and install on your computer.
2. Set a Source. You must set the source - Video Capture Device, and choose the camera your computer.
3. Under Settings -> **Stream**. a. Pick Service -> **Custom**. 
4. Enter the following parameters: b. Server: **rtmp://broadcast.api.video/s** c. Stream Key: **enter the StreamKey Value you obtained from creating your class**.
5. Click **Start streaming**.  

The live stream is available on your portal!  When you stop streaming, the video will be placed below the line into the recorded video list.

api.video transcodes your video to much smaller sizes and bitrates. Even if you are sharing a 4K video, your customers or students on very slow connections will still be able to watch on a 250 kbps 240p, or 500 kbps 360p video. Sure, it won't be beautiful, but hey can participate. And to top it all off, all the video sare saved in a conveient portal for later viewing.

## You May Also Like
* [Start and Record a Live Stream of Your Zoom Meeting](https://api.video/blog/no-code/start-and-record-a-live-stream-of-your-zoom-meeting) - Add a live stream to your Zoom meeting so you can reach more viewers, then save a high quality playback for anyone who wants to watch later.
* [Live Stream to the Browser with FFMPEG CLI and Python](https://api.video/blog/tutorials/live-stream-to-the-browser-with-ffmpeg-cli-and-python) - Create a live stream using Python and the FFMPEG command line. 

Article reposted from Glitch by Erikka Innes

Start and Record a Live Stream with OBS

As COVID-19 is forcing more educators to teaching remotely, and more organisations are cancelling in-person meetings, video conferencing is becoming more important than ever.

With entire countries under lockdown or quarantine, tools like Zoom, Skype, Hangouts and others are seeing high usage. However, these tools can have high bandwidth requirements. Zoom recommends 800 KBPS up and 1 MBPS down for group conferencing.

What about students who do not have fast internet at home? Advice like "Go to the library" just doesn't work during a pandemic. How can the video be served at a lower bitrate for these users?


## Live Transcoded Streams
For streamers (professors, teachers, colleagues), there are settings that will push the video to live transcoding engines. In this example, we'll use api.video to transcode the video to a lower bitrate.

## Saving Videos for Later Playback
IF you are streaming the videos, wouldn't it be great to also aggregate these videos into a portal for your students to later review? Zoom allows you to record your videos, and provides you a URL, but then you have to create the portal. What if we could create the cortal from the LIve Stream?

## Simple Setup
As we walk through this process, you'll see that this is an easy setup that anyone can use to share their live video streams.

## Getting Started
To begin, go to [api.video](https://api.video) and create a free account. Once you sign up, you'll see a list of keys. You'll need your production key in a few steps, so make note of it (or leave the dashboard open in a window to come back to).

The code for this project is hosted at Glitch. All Glitch apps get a silly subdomain (in this case ["twilight-decorous-mail"](https://glitch.com/~twilight-decorous-mail)). 

1. On the Glitch page, click **View Source**.
2. Click the button **Remix to Edit**. You'll have your own version (with silly name).
3. On the left menu are all the files that create the website. Click on the **.env** line (there is a key next to it). This file will open in the middle. On lines 8, and 10 are three variables: imageUrl, apiVideo and PORT. There is no value after the equals sign. For **imageUrl**, add a url pointing to your logo. For **apiVideo**, paste in the production key from when you signed in. For **PORT** enter **3000**.

That's it - you just configured your website. Now to add your content:

1. At the top, click the **sunglasses**, and open the project in a new page. You'll see a mostly empty site. We haven't configured it yet. 
2. In the url bar, after the https:-silly-.glitch.com add **/createClass** to the end and press **Enter**. You'll get a page about creating a class. 
3. On this page, you can enter your class name, and also whether you want to record all sessions for later viewing. Press **Enter**, and you'll get some more important information: your StreamKey and the URL of your site with a URL parameter afterwards. Make a note of these as you'll need them for the next set of instructions.

## Now we are ready to stream with Zoom!!
To get any content on the page, we need to start streaming. 
	
1. Login to Zoom.us.
2. Go to your **Account Settings**.
3. Under Meetings, there's a setting called **Allow live streaming meetings**. Enable this setting.
4. Start your meeting and under More choose **Live on Custom Live Streaming Service**.
5. For Streaming URL put: rtmp://broadcast.api.video/s
6. For Stream Key put:  StreamKey value obtained from above.
7. Enter the website url to your video portal.
8. Click **OK**.

The live stream is now available on your portal. When you stop streaming, the video will be placed below the line into the recorded video list.

api.video transcodes your video to much smaller sizes and bitrates. Even if you are sharing a 4K video, your customers or students on very slow connections will still be able to watch on a 250 kbps 240p, or 500 kbps 360p video. Sure, it won't be beautiful, but hey can participate. And to top it all off, all the video sare saved in a conveient portal for later viewing.

You can also view your live stream and recorded live stream through your api.video dashboard in the section for live videos.

## You May Also Like...
* [Livestream a video](https://a.video/works/livestream-a-video) - This is a demo you can try without coding, hosted at a.video! 
* [Secure live streams with unique overlay](https://api.video/blog/tutorials/secure-live-streams-with-unique-overlay) - Learn how to secure live streams so they aren't shared when they shouldn't be.
* [Live stream from your Android Phone](https://api.video/blog/tutorials/livestream-from-your-android-phone) - Create a live stream using your Android phone.

Article reposted from Glitch by Erikka Innes.

Start and Record a Live Stream of Your Zoom Meeting

Walkthrough set up for sending details about a newly uploaded video to Google Spreadsheets. Later, you can review the spreadsheet to make sure you uploaded everything, and the settings for each video are correct. If they aren't, you can take data from your spreadsheet and use it to make changes to your videos more easily, either with one of our helpful PHP scripts that let you update data in bulk, with a custom script of your own, or even your very own no-code Zap! 

## Prerequisites 
You'll need these things to successfully complete this project:

* [api.video account](https://dashboard.api.video/register)
* Google account
* Zapier account
* This tutorial assumes familiarity with Zapier. If you're not sure what Zapier is, please review the post [Create Video Integrations Without Coding - So Easy It's a Zap!](https://api.video/blog/no-code/create-video-integrations-without-coding-so-easy-it-s-a-zap/) to learn about triggers and events. We will briefly review them as they come up here.


## Configure api.video as a Trigger Event
To get started, you need to configure api.video as the trigger event for sending an email. In Zapier, the trigger event is something that occurs with the chosen product that results in you wanting to take action. In this case, whenever a new video is created in api.video, we want something to happen. 

1. Make sure you've added a sample video to your account for testing. You should add it right before trying this tutorial. If you haven't, add something to test with now. We're using production here, so you'll want to add a video to your production environment before starting. If you need a sample, you can choose one from here: [Sample Videos for Download](https://www.learningcontainer.com/mp4-sample-video-files-download/)
2.You're prompted to choose your account. If you're already connected because you tried out a different zap with api.video, you'll see your account as a choice. Otherwise, you'll see **Sign in to api.video**. Click this option.
3. You're asked if Zapier can have access to your api.video account. Enter your API key to get started. If you choose your production API key, you'll receive an alert whenever you add a new video to production on your account. If you choose your sandbox API key, you'll receive an alert whenever you add a new video to your sandbox. NOTE: You can get the key you want from [dashboard.api.video](https://dashboard.api.video).
4. After you enter your API key, click **Yes, Continue**.
5. You'll see your account listed with the start of your authorization token if all goes well. Click **Continue**.
6. Now it's time to set up your trigger. From the **Trigger Event** drop-down, select **New Video**. 
7. Click **Continue**.
8. Leave the Title and Tags fields empty. 
9. Click **Continue**.
10. You can now test your trigger. Click **Test trigger**. If all goes well, you get a response saying 'We found a video!' If not, the recommendation is to add a video to your account. Make sure you've added the video to right part of your account! You can add a video and try again. You can also clear your browser cache and try again. If it continues not working, contact us on Intercom (use the chat balloon on our [docs](https://docs.api.video/reference) page or our [website](https://api.video/) or our [community forum](https://community.api.video/)).

## Configure Google Spreadsheets as Your Action Event
Now we'll configure so Google Spreadsheets is the action event. In Zapier, an action event is a response to a trigger event. When api.video sends notification that a new video is created, Google Spreadsheets responds with an action event - which is adding data about the new video to the spreadsheet.

1. For Google Sheets, everything populates in the Action. You should see Google Sheets listed for Choose app & event. Underneath you can choose what action event you want for this application, and it should already show Create Spreadsheet Row. If it doesn't, choose these options from the drop-downs.
2. Click **Continue**. 
3. You are prompted to sign in to Google Sheets. Click the **Sign in to Google Sheets** button.
4. You are prompted to choose the account you want to sign in with. Choose the account you want to use, or add it.
5. You're asked to grant the right to edit, create, and delete all of your Google Drive files as well as the right to edit, create, and delete spreadsheets in Google Drive. Click **Allow**.
6. Click **Continue**. You can now set up details about your action.
7. The details you can set for your action are: 
* Drive - The area from your Google Drive you want to take a spreadsheet from.
* Spreadsheet - Choose the spreadsheet you want to use from the drop-down.
* Worksheet - Choose the specific worksheet to use from the spreadsheet you chose.
* There's now three fields - Id, Title, Description. In each box, choose the piece of data that matches. These will dynamically populate in the spreadsheet. If you mess up, you can click **Refresh fields** to start over again. 
8. Click **Continue**. Zapier sets up a test action for you. 
9. Click **Test & Continue**. If there's an issue, and Zapier can help with the error, it will give you a message about what to fix. Otherwise, you should get a message saying 'Test was successful!' 
10. If you like your new zap, click **Turn on Zap** to start using it! 

If there's a zap you'd like to see us make, please contact us in our [community forum](https://community.api.video/)! 

zapier, api.video, google sheets, integrate google and api.video

large_videogooglesheet.png

medium_videogooglesheet.png

small_videogooglesheet.png

thumbnail_videogooglesheet.png

videogooglesheet.png

Update a Google Spreadsheet Every Time You Add a Video to api.video (Zapier)

Video upload

This tutorial shows you how to configure Zapier so that whenever you add a new video to api.video, an email is sent notifying people. This is a no-code solution, you just follow the configuration steps to combine the applications using Zapier. If you've created an api.video zap before, you can skip ahead to the section 'Configure Gmail as Your Action Event.' 

## Prerequisites 
You'll need these things to successfully complete this project:

* api.video account - if you don't have an accunt, you can create one [here](https://dashboard.api.video/register).
* Gmail account
* Zapier account
* This tutorial assumes familiarity with Zapier

You can check out the webhook used for this project in the api.video API reference documentation: [Webhooks](https://docs.api.video/reference/list-webhooks)

api.video, gmail, zapier, email notifications when video is uploaded

large_chooseintegration.png

medium_chooseintegration.png

small_chooseintegration.png

thumbnail_chooseintegration.png

chooseintegration.png

## Configure api.video as the Trigger Event
To get started, you need to configure api.video as the trigger event for sending an email. In Zapier, the trigger event is something that occurs with the chosen product that results in you wanting to take action. In this case, whenever a new video is created in api.video, we want something to happen. 

1. Make sure you've added a sample video to your account for testing. You should add it right before trying this tutorial. If you haven't, add something to test with now. We're using production here, so you'll want to add a video to your production environment before starting.
2. You're prompted to choose your account. If you're already connected because you tried out a different zap with api.video, you'll see your account as a choice. Otherwise, you'll see **Sign in to api.video**. Click this option.
3. You're asked if Zapier can have access to your api.video account. Enter your API key to get started. If you choose your production API key, you'll receive an alert whenever you add a new video to production on your account. If you choose your sandbox API key, you'll receive an alert whenever you add a new video to your sandbox. NOTE: You can get the key you want from [api.video dashboard](https://dashboard.api.video/register).
4. After you enter your API key, click **Yes, Continue**.
5. You'll see your account listed with the start of your authorization token if all goes well. Click **Continue**.
6. Now it's time to set up your trigger. From the **Trigger Event** drop-down, select **New Video**. 
7. Click **Continue**.
8. Leave the Title and Tags fields empty. 
9. Click **Continue**.
10. You can now test your trigger. Click **Test trigger**. If all goes well, you get a response saying 'We found a video!' If not, the recommendation is to add a video to your account. Make sure you've added the video to right part of your account! You can add a video and try again. You can also clear your browser cache and try again. If it continues not working, contact us in our [community forum](https://community.api.video/)).

## Configure Gmail as Your Action Event
Gmail is going to provide our action event. In Zapier, an action event is a response to a trigger event. When api.video sends notification that a new video is created, Gmail responds with an action event - which is sending an email to a list of selected recipients stating that the video is now available.

large_gmailsetup.png

medium_gmailsetup.png

small_gmailsetup.png

thumbnail_gmailsetup.png

gmailsetup.png

Thanks for trying out the walkthrough with us today! 
Don't hesitate to ask questions on our [community forum](https://community.api.video/) or [start building](https://dashboard.api.video/register) now and integrate your videos without any code!

api.video, gmail, zapier, connect api.video with gmail

large_apigmail.png

medium_apigmail.png

small_apigmail.png

thumbnail_apigmail.png

apigmail.png

Get Notified By Gmail When a New Video is Available (Zapier)

Now you can combine api.video with all your favorite applications without doing any coding! We are proud to announce that we've partnered with Zapier. 

Zapier allows you to integrate your favorite applications without any coding at all. Perhaps you don't program, but you have a cool idea for how to use api.video services with another application, or maybe you want to do a proof-of-concept before you code your idea. Zapier will let you do it all. 

## How Does Zapier Work? 
When you sign up for an account with Zapier, you'll learn about three concepts:
* Zap
* Trigger
* Action 

A  Zap is an application you build using Zapier. It's composed of at least one trigger and one action that occur between two different products.

A trigger is an event that kicks off a zap. For example, a trigger event could be you uploading a video to api.video. When a trigger event occurs, that's the cue for an action to happen. 

An action is what happens in response to a trigger. Say you have the trigger event of a video being added to api.video. A response action could be sending you a text message to alert you that there's a new video. 

## How do you set up Zapier with api.video?

medium_zapwelcome.jpg

small_zapwelcome.jpg

thumbnail_zapwelcome.jpg

zapwelcome.jpg

As you can see in the image, once you are logged in Zapier, what you'll be doing is choosing two applications and transferring information between them. 

The application you choose for the left side is going to be your trigger event. The application you choose for the right side is going to respond to the event by taking action. 

Generic set up will include these steps: 

1. [Sign up](https://dashboard.api.video/register) for an api.video account. 
2. In Zapier, choose api.video for your trigger event. 
3. Set up the trigger event. You're provided with instructions for what to do every step of the way.
4. Choose the application for your action event. 
5. You'll again need to have an account with the application you select, and the appropriate privileges for what you want to do.
6. You'll have the opportunity to test the parts of your app as you go along.
7. At the end, you'll be able to do a test run of the completely new integration you've made between applications. 
8. You can turn on your zap, and it will start running every time the trigger event occurs! 

## You May Also Like...

Some examples for you to consider: 

* [**Receive a text message every time a new video is uploaded**](https://api.video/blog/no-code/it-s-a-zap-upload-a-video-and-receive-an-sms-notification) - This would be great if you want to stay up-to-date with breaking news clips, the latest episode of your favorite TV show coming out, or whenever someone on your team completes a new video project. 
* [**Send a slack message about a new video upload**](https://api.video/blog/no-code/send-messages-in-slack-any-time-you-create-a-new-video) - If you have a workflow where other team members need to know a new video is available for them to edit, you can notify them in slack about every upload. 
* [**Send an email notification about new videos**](https://api.video/blog/no-code/get-notified-by-gmail-when-a-new-video-is-available-zapier) - Send a note through Gmail every time you upload a new video to api.video.

large_zapier-api-video.jpg

medium_zapier-api-video.jpg

small_zapier-api-video.jpg

thumbnail_zapier-api-video.jpg

zapier-api-video.jpg

Create video integrations without coding - So easy it's a Zap!

There are lots of reasons you might need to immediately know that a video's been added to a collection. Maybe you're on a tight deadline, and you need to know when a set of videos becomes available so you can start your project. Maybe you're following a TV show, and want to know when the next episode is available. Or maybe you're interested in when the latest news event gets posted. Any of these, or many other reasons could lead to you wanting to receive an SMS alert when a video gets posted. 

Using Zapier, we'll walk through a no code method for receiving an SMS alert when a new video is uploaded to your api.video account. Let's get started! 

## Prerequisites 
You'll need a few things to successfully complete this project:

* api.video [account](https://dashboard.api.video/register)
* Upgraded Twilio account
* Paid for phone number that you can send SMS from
* Verified number (your cellphone) you can receive text messages with

Twilio will walk you through everything and we provide links to the content you'll need to set yourself up with Twilio.

This project uses webhooks, so you can check out the API reference documentation for this here: [Webhooks](https://docs.api.video/reference/list-webhooks)


## Configure api.video as the Trigger Event
Set up api.video so it will provide a trigger event for Twilio. 

1. Make sure you've added a sample video for testing. We're using production here, so you'll want to add a video to your production environment before starting.
2. Log in to Zapier.
3. Go to [https://zapier.com/apps/apivideo/integrations/twilio](https://zapier.com/apps/apivideo/integrations/twilio). 
4. Next to Send Twilio SMS messages for new videos in api.video click **Try It**. The configuration process starts.

medium_start.jpg

small_start.jpg

thumbnail_start.jpg

start.jpg

5.  You're prompted to choose your account. If you're already connected because you tried out a different zap with api.video, you'll see your account as a choice. Otherwise, you'll see **Sign in to api.video**. Click this option.
6.  You're asked if Zapier can have access to your api.video account. Enter your API key to get started. If you choose your production API key, you'll receive an alert whenever you add a new video to production on your account. If you choose your sandbox API key, you'll receive an alert whenever you add a new video to your sandbox. NOTE: You can get the key you want from [my.api.video](https://dashboard.api.video/register).
7.  After you enter your API key, click **Yes, Continue**.
8.  You'll see your account listed with the start of your authorization token if all goes well. Click **Continue**.
9.  Now it's time to set up your trigger. From the **Trigger Event** drop-down, select **New Video**. 
10.  Click **Continue**.

medium_apitrigger.jpg

small_apitrigger.jpg

thumbnail_apitrigger.jpg

apitrigger.jpg

11. Leave the Title and Tags fields empty.  
12. Click **Continue**.
13. You can now test your trigger. Click **Test trigger**. If all goes well, you get a response saying 'We found a video!' If not, the recommendation is to add a video to your account. Make sure you've added the video to right part of your account! You can add a video and try again. You can also clear your browser cache and try again. If it continues not working, contact us on Intercom (use the chat balloon on our [docs](https://docs.api.video/reference) page or our [website](http://api.video/) or our [community forum](https://community.api.video/)). 

## Configure Twilio as Your Action Event
Now it's time to configure everything for Twilio. 

1. Sign up for a Twilio account. 
2. Upgrade your Twilio account.
3. Buy a phone number with Twilio.
4. Leave your Twilio account open on the dashboard, and go back to Zapier. 
5. Click **Action Send SMS in Twilio**.
6. If you've connected Twilio to something previously, you'll see your account as a choice in the drop-down for an event. Otherwise you'll get **Sign in to Twilio**. 
7. Go to the Twilio dashboard you left open, and grab your authentication information. You'll need your **Account SID** and your **Auth Token**. 
8. Add your Account SID and Auth Token to the appropriate fields in Zapier's prompt. Click **Yes, Continue**. 
9. From the Action Event drop-down, choose **Send SMS**. 
10. Click **Continue**. 
11. In the Set up action section, click under the **From Number** drop-down. The phone number you bought should be listed. Click to select it. Optionally, if you'd like to enter an Alphanumeric Sender ID to receive your message from, you can provide it. However, it's not often this ID is used, so you can also skip it.
12. For **To Number** enter the phone number you set up your Twilio account with. Make sure you put your complete phone number, with no special characters or spaces. NOTE: You can use other numbers as well, but you have to add them to your Twilio account. It's easier for the walkthrough to use the number you signed up with.
13. In the **Message** field, check that the message is alright. You can enter whatever text you like, and then you can dynamically add variables to display from the list provided under the Message field. For our walkthrough, go ahead and leave the message that's provided. 
14. Click **Continue**.
15. Now you'll be asked to test your action. Click **Test & Continue**. If all goes well, you receive a text message on your phone about a new video using the sample we selected for the api.video section. 
16. You're all set, the last thing is to try this out for real. Click **Turn on Zap**.

Now that you've tried creating a zap with some help, maybe you'll want to try something out on your own! 