Video list

Normal

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

Tutorials

Today we'll learn how to grab video data from api.video, add it to a database, then use that information to create an infinite wall of videos that you can keep scrolling through.

large_infinitevideos.jpg

medium_infinitevideos.jpg

small_infinitevideos.jpg

thumbnail_infinitevideos.jpg

infinitevideos.jpg

For this project, we're going to also use Laravel 8. 

## Prerequisites

* api.video account - [Register here](https://dashboard.api.video/register)
* [Laravel 8](https://laravel.com/docs/8.x/installation) installed
* Project repository - [https://github.com/apivideo/api.video-php-client/tree/main/examples/laravel/infinite_scroll](https://github.com/apivideo/api.video-php-client/tree/main/examples/laravel/infinite_scroll)
* api.video [PHP client](https://github.com/apivideo/api.video-php-client) 
* Symfony HTTP client - `composer require symfony/http-client` 
* composer - [https://getcomposer.org/](https://getcomposer.org/)

## What you'll be doing
You have three tasks for this project: 
1. Retrieve your data from api.video
2. Add your data to your database
3. Set up your page to show the videos in an infinite scroll 

## Retrieve your data
You need to collect some data from api.video about the videos you're going to use. To keep it simple, for this walkthrough I'm just retrieving videos tagged 'holiday' and keeping the title, video ID, and MP4 link for each one. You can retain any information you might want to use or display, the most important thing is the MP4 link. 

For this part of the project, I didn't use Laravel 8, I just set up a php file with my code and used composer. 

After you run the code, you'll have a list of all videos from your account that you tagged **holiday** in a .csv file. Save the file, we'll use it for the next part of our project.

## Set up your project
Now it's time to set up our Laravel 8 project. We'll need this before we can do anything with our database. These instructions are for Macs.

1. Make a new project by opening a terminal in the place where you want to store your project by typing `laravel new holiday`. 

2. Install the api.video PHP client. `composer require api-video/php-api-client`

3. Install the Symfony HTTP client. `composer require symfony/http-client`

4. Go into your project and find the .env file. For the section that starts **DB_** delete every **DB_** item except for **DB_CONNECTION**. Set **DB_CONNECTION** to sqlite. `DB_CONNECTION=sqlite`

5. Create a database table for the .csv file we made. `php artisan make:migration create_holidays_table`

6. Go into your project in the database folder and open the migrations folder. There should be a .php file with a timestamp at the start followed by the name of the table you just created in the terminal. Open this file and paste in this code:

7. Migrate your new table. `php artisan:migrate` 

8. Now we're going to create two models. The first is for handling infinite scroll. `php artisan make:model Model/InfiniteScroll` 

9. After you've made this model, go find it in your project and paste in this code: 



10. The second model we're going to make is for setting up our Holidays table contents. `php artisan make:model Model/Holiday`

11. Navigate to your new Holiday model and paste in this code:



12. Let's create a seeder that we can use to populate our new table using our .csv file. `php artisan make:seeder HolidaySeeder` 

13. Take your .csv file and place in the data folder for your database. 

14. Go to the seeders folder and open your HolidaySeeder.php file. Paste in this code:

15. Now we can run our seeder! `php artisan db:seed --class=HolidaySeeder` This should populate your database with the information from your .csv file. We're ready to set up our page to display our video collection. 

## Display videos
In this section we'll set up routes, a controller, and the page that will display videos whose links are retrieved from our database. 

1. We're going to add a new route, but before we do that, navigate to RouteServiceProvider.php. Scroll down to the line that reads `protected $namespace = 'App\\Http\\Controllers';` - it's probably commented out. Remove the commenting so it is active again. 

2. Navigate to routes\web.php. Add a new route `
Route::get('/load-more-data', 'VideoController@InfiniteScroll' );`

3. Make a new controller. `php artisan make:controller VideoController` 

4. Navigate to Controllers and open your VideoController file. Paste in this code:

5. Now let's set up our blade file. Navigate to views and craete a new blade file called **holidayView.blade.php**. Open the new file and paste this in: 

6. If you don't have a **data.blade.php** file, create one in the same folder as your other blade files. Open **data.blade.php** and paste in this code: 

## Run your project

Open a terminal in your project and type `php artisan serve`. You should be able to see a list of scrolling videos! 

If you have any questions about this tutorial, or would like to share what you've built, please join our [community forum](https://community.api.video/). 

Create an infinite scrolling wall of holiday videos with Laravel 8

large_create-an-infinite-scrolling-wall-of-holiday-videos-with-laravel-8.jpg

medium_create-an-infinite-scrolling-wall-of-holiday-videos-with-laravel-8.jpg

small_create-an-infinite-scrolling-wall-of-holiday-videos-with-laravel-8.jpg

thumbnail_create-an-infinite-scrolling-wall-of-holiday-videos-with-laravel-8.jpg

create-an-infinite-scrolling-wall-of-holiday-videos-with-laravel-8.jpg

Video upload

api.video offers a PHP client to make it easier for you to upload your videos. Today we'll walk through how to do this. You can always hop on over to the GitHub repository if you'd prefer to learn about the client that way too - [api.video PHP client](https://github.com/apivideo/php-api-client).

## Prerequisites

For this project, you'll need these things: 

* Composer - if you don't have it set up, go here to learn about it and get it installed - getcomposer.org
* An api.video account - you can sign up [here](https://dashboard.api.video/register).

## Installation

You'll need to install a few things using Composer:

* The api.video PHP client - `composer require api-video/php-api-client`
* Symfony HTTP client - `composer require symfony/http-client`
* nyholm/psr7 - `composer require nyholm/psr7`

You can type **composer update** to make sure everything is pulled into your project and configured. 

## Code sample

Here is the code sample for uploading a file. You need to change **'yourAPIkey'** to your key that you retrieve from the api.video dashboard after you create an account. Place the video you want to upload in the same folder as your code sample. For the sake of simplicity, this code sample hardcodes the title of the video - change **VIDEO_TO_UPLOAD.mp4** to the title of your video file.

### Import the client
In the first part of the code, you import the parts of the api.video PHP client you'll need. The client is more efficient when you import the endpoints you need for your code, instead of everything. You also need the HttpClient from Symfony for this implementation. So it will look like this:

## Initialize the client 
Next you initialize the client for use in your API calls. 

## Create your video payload 
The next part of the code includes a video creation payload. This is a cool part of the PHP client. You can add all the metadata you'd like for your video here. Later, you're able to update your code as well. Consult the [Create a video](https://docs.api.video/reference/post-video) endpoint in our API reference documentation for available parameters. You capitalize them when adding them into your payload. So title becomes `setTitle` as shown in the code sample. Any parameters in camel case that you want to use would change a bit. For example, the docs have mp4Support, but if you are using the PHP client, you would write it as `setMp4support`. 

When you send multiple parameters, the code would look like this: 

`$payload = (new VideoCreationPayload())
    ->setTitle('My cool video');
$payload->setTags(['tag 1', 'tag 2']);`

When you're done setting up your payload, then you use the client to send this information to api.video servers and create your video container.

## Upload the video
In the last part of the video, you retrieve the video ID for the container you made and upload your video into the container. You can only upload into a container once, but you can change its metadata later if you wish. You can see whether it worked by reading the echoed response in the terminal.

## Conclusion
Now you know the basics of uploading a video with the api.video PHP client! You can check whether your upload worked by going into your dashboard and looking in the videos section. You should see it there. If you get a note that it's still processing, give it a bit of time to get the video ready, especially for big videos. 

If you have any questions or suggestion, please share them on our [community forum](https://community.api.video/). If you haven't created your api.video account yet, you can do that in just a few moments by follwoing [this link](https://dashboard.api.video/register). Happy building! 

small_denise-jans-lq6rcifgjou-unsplash.jpg

thumbnail_denise-jans-lq6rcifgjou-unsplash.jpg

denise-jans-lq6rcifgjou-unsplash.jpg

Upload a video with the api.video PHP client

video create

The first step to displaying your video online is getting it uploaded. Today we'll go over how to upload a video using Laravel 8 with api.video's PHP Client. Before we dive in, let's go over what we'll be doing when we upload a video. 

Uploading a video is a two step process. First, we create a container for the video and retrieve the video ID. Then, we upload a video into the container by referencing the ID. You can only upload a video to a container once, but you can modify details about the video at any time after that. Our uploader will let you add a title, description and list whether you want to have the video be public or private and whether you want to offer an MP4 link of the video for download. 

## What you'll need 
To get started, make sure you have these things:

* Account with api.video - you can sign up [here](https://dashboard.api.video/register)
* Laravel 8 - you can use other versions, but some things work differently
* NPM and node.js - you install these when you set up Laravel 
* Composer - you'll need this installed 
* [api.video PHP client](https://github.com/apivideo/php-api-client)
* Project repository - [https://github.com/apivideo/php-api-client/tree/main/examples/laravel/video_upload](https://github.com/apivideo/php-api-client/tree/main/examples/laravel/video_upload)

You can also review the API reference documentation for the endpoints used in this project: 
* [Create a video](https://docs.api.video/reference/post-video)
* [Upload a video](https://docs.api.video/reference/post_videos-videoid-source)

## Create your project
The first thing you'll need is a Laravel 8 project to work with. Here's what I did:

1. In a terminal make a new project by typing: **laravel new fileuploader** or similar project name.
2. Open your project folder, you'll need to install a few things.  
3. You'll need to add the api.video PHP client, so at the terminal type: **composer require api-video/php-api-client** 
4. You'll also need the symfony http client, at the terminal type: 
**composer require symfony/http-client**
5. And the last thing to add is nyholm/psr7:
**composer require nyholm/psr7**

You can type **composer update** to make sure everything is pulled in to your project and configured.
 
## Create a controller
We will need a controller for our video uploader, so let's go ahead and do that now. In the terminal in your project folder type: 

**php artisan make:controller UploadController** 

This will automatically create what we need to start building the controller. 

## Set up the home page with an upload form
For this walkthrough, we're using the home page to create an upload form. So in your views folder, go into **home.blade.php** and create the form. I selected to allow the user to add basic details about their project. I'm also using bootstrap, so the basic form looks like this: 

Image of upload form showing available fields

large_viduploadphp.png

medium_viduploadphp.png

small_viduploadphp.png

thumbnail_viduploadphp.png

viduploadphp.png

And here is the code that creates this form: 

We pull in the bootstrap details up top under the Scripts and Styles sections. Then for our form, we have all the form data sent in a POST request to the '/upload' route. (We'll need to create that route in a moment.) 

The form is straightforward - we list the type of data as text for the name of the file and the description of the file. For choosing whether the file will be public or offer an MP4 for download, we use a radio button, so the type is radio. For the video, we choose type file and then we set up our submit button. Bootstrap styles everything for us, so we're all set here. Now we need to handle the route. 

## Set up the /upload route
Open your **web.php** file and add a new route: 

**Route::post('/upload', 'UploadController@upload');** 

This route indicates that when submit is clicked in the form, it should go to /upload and carry out the upload instructions listed for the UploadController. 

We don't have that set up yet, so let's do that next. Also, the other routes are added into the project, you can see everything if you download the repository.

## Set up your UploadController
Our controller takes the details provided by the form, then uploads the content to api.video. Behind the scenes, we're going to need our api.video API key, so let's make sure we handle it securely. 

1. Go to your .env file. In the top section, you'll see items to do with your app. At the bottom of the list of items beginning **APP_** you'll see **APP_APIVIDEO=yourapikey**. Replace **yourapikey** with your key (retrieve it from your api.video dashboard). Don't add quotes. 
2. Open **RouteServiceProvider.php**.
3. In the file, take the commenting **\\** off of the line **protected $namespace = 'App\\Http\\Controllers';**. This returns the use of the automatic namespace, which is handy.
4. Open **UploadController.php**. 
5. Add this code: 


In our code, we set up the api.video client and collect the information from the request object that comes in from the form. We check if the data for the radio buttons is set and if it is, we add it to our payload for upload. Then we send the data and redirect the user to a page that says 'Success!' 

## Conclusion
These are the basics for uploading a video to api.video. You can try using different styles or set ups if you want to allow users to add more metadata on upload. If you have any questions or suggestions, please share them on our [community forum](https://community.api.video/). Thanks for reading! 



Upload a video with Laravel

Laravel is a great framework for building web applications. It does a lot of the heavy lifting for you, so you can focus your development efforts on the more unique elements of your application. Because there are multiple versions of Laravel and many of the packages you'll use with it have their own updates, it can sometimes get tricky to troubleshoot. There are many troubleshooting suggestions online, and this quick article aims to help sift those for the best tips. 

## Check your version of Laravel
One issue you will encounter is matching your version of Laravel to the advice you find online. This guide may work for other versions of Laravel, but is intended for Laravel 8. When troubleshooting, make sure you are conscious of what version you have and what version the tips you find are for.

## Bootstrap isn't working in my Laravel project
You must properly install Bootstrap for your Laravel project in order to add it to your files. If you find that Bootstrap styling isn't appearing on your HTML pages as expected, this section may be for you.

### How to install Bootstrap 4 for Laravel
To install Bootstrap 4 for your Laravel project, you do these things: 

1. At the command line, type `composer require laravel/ui`.
2. At the command line, type `php artisan ui bootstrap` if you just want Bootstrap for your project but don't plan to do any authentication. If you want to handle authentication in your project with bootstrap, then type `php artisan ui bootstrap --auth`. 
3. You'll also need to make sure npm is installed, so at the command line, type `npm install`.
4. Finally, at the command line run `npm run dev`.  

Some problems that might arise are having packages that aren't up to date, or issues with installing Laravel Mix. You can search online for how to handle packages that aren't up to date if there's a special issue. For the Laravel Mix issue, simply run `npm run dev` again. It often solves the issue.

### How to add Bootstrap 4 to your blade files 
To add Bootstrap 4 into your **blade.php** files, you use mustache quotes {{}} to reference the Bootstrap content you'll need. It looks like this: 

You may see the choice where you just reference a link to a public distribution, but blade files work differently. You need to use the mustache quotes version to add the files.

### Bootstrap still isn't working 
You'll see a note on installation that you don't have the most recent version of popperjs. If you want to update that to see if it corrects your issue, you can use the following command: 

`npm i @popperjs/core` 

## I don't see the changes I made to SASS and JS
If you don't see changes implemented in your application after updating something in SASS or JS files, the issue might be that you didn't run `npm run dev` again. Every time you change content here, you must use this command. If you don't want to do that and want to continually see your changes while you're making them, you can use `npm run watch`. This command will start regularly checking your files and recompiling every time it detects new changes. 

## I made changes to my application and they're not reflected on my server
If you made changes that are not just updates to the views, you may need to restart your server. You can do that like this: 

1. Press **Control + C** at the same time.
2. Type in the terminal in your project folder `php artisan serve`. 

## I installed a new library 
If you install a new library with Composer, you need to make sure you pull in all the new changes that causes. In the terminal type: 

`composer update` 

## I made changes to my database schema 
If you change your database schema or add something new, you need to run a migration. This is pretty simple, type: 

`php artisan migrate:fresh`

## My application isn't accessing my public folder correctly
To make sure your application accesses your public folder, which is where you'll often store assets, you need to create symbolic links for your application: 

`php artisan storage:link` 

## I'm still not sure why I can't see changes I made
If you get stuck, an easy thing to try is: 

`php artisan config:clear` - this clears your cache file. If you corrected something, but the cache isn't cleared, you might not be able to see your update. 

## The route I want isn't displaying
The order of routes in your **web.php** file matters! If you put routes that include variables first, it can mess up the flow of your application. Try to put concrete routes first, and then routes with flexible components after. 

## My controllers aren't found
In Laravel 8, the automatic namespace is turned off. If you want the same functionality as earlier versions of Laravel back, go to **RouteServiceProvider.php** and make it so `protected $namespace = 'App\\Http\\Controllers';` is no longer commented out.

## Conclusion 
When working with Laravel, there are lots of small details to remember. Updating and refreshing various aspects of your application can help correct a lot of problems you may encounter. If you want to try building something with api.video and Laravel, check out our post [Create your own version of Instagram using api.video and Laravel](https://api.video/blog/tutorials/create-your-own-version-of-instagram-using-api-video-and-laravel).

medium_laravel8logo.png

small_laravel8logo.png

thumbnail_laravel8logo.png

laravel8logo.png

Troubleshooting tips for your Laravel 8 project

If you've ever wanted to take the time to learn how to build your own social media platform, this tutorial will get you started. Using the incredible [Laravel PHP framework tutorial](https://youtube.com/watch?v=lmtZ5yENzgE) from Victor Gonzalez, you can set up the basics for Instagram. However, his tutorial doesn't include video support. That's the tweak I'm providing today with this tutorial. 

If you want a complete version of Instagram, things you'll need to add yourself are: 
* More robust population for a person's page when it opens, for example linking to their profile instead of typing the number (which you'll know since there won't be many users when you set it up) to go to your profile or someone else's. 
* Ability to delete images and videos. 
* Search capability. 
* Algorithm for what to prioritize showing someone in their feed if there's lots of followers. 
* More robust database. 
* Move email out of test mode to actual email that's sent. 

Let's get started! 

## Installation 

For this project, you should be familiar with Laravel already, or willing to go through Victor's 4 hour tutorial to learn everything you'll need. Make sure you have these things ready:

* Composer - [https://getcomposer.org/](https://getcomposer.org/)
* Node.js - [https://nodejs.org/en/](https://nodejs.org/en/) 
* NPM - this is installed for you with Node.js 
* Laravel - [https://laravel.com/docs/8.x](https://laravel.com/docs/8.x) - this project uses 

To get the tutorial version of the code to work with, go to [https://github.com/coderstape/freeCodeGram](https://github.com/coderstape/freeCodeGram). If you want the code with the api.video tweaks included, and the tutorial completely put together, then go here: [https://github.com/apivideo/freeCodeGram](https://github.com/apivideo/freeCodeGram).

The next part of installation will require you to clone the github repository and then configure the project. There is a great walkthrough here: [How to Setup a Laravel Project You Cloned from Github.com](https://devmarketer.io/learn/setup-laravel-project-cloned-github-com/). There are some steps you won't need, the steps you need to follow are: 1, 2, 4, 5 (I recommend not using yarn), 6, 7, 8, 9 and 10. 

For step 8, this project uses a flat SQLite file for the database. To set this up, go into your project and type: 

```vim database/database.sqlite``` 

After it's created, save it without typing anything into the file. 

Then go to step 9, and make sure the information is filled out appropriately for the database (it should be). The correct set up is just to have DB_CONNECTION=sqlite. There should be no other DB_ items listed. 

Follow step 10. You're done with the walkthrough! There's just a couple more configuration things to do. 

### Authentication 

You'll need to go into php artisan and run the ui:auth command: 

```php artisan ui:auth``` 

### Storage 

You will need to go into freeCodeGram/storage/public and add an uploads folder. 

You may need to run the storage:link command as well: 

```php artisan storage:link``` 


### Set up your php.ini file 

If you want to handle videos that are 10 MB or more, you have to change the settings for what you can and can't upload. To do this, check the status and location of your file first: 

```php --ini``` 

This will bring back the location of the file, in the line: 
```Configuration File (php.ini) Path: /etc```  
or something similar. 

It'll also bring back the line: 
```Loaded Configuration File:``` 
with details after it. The details will either list the configuration file that's loaded, or it will show that there isn't one at all. 

It's recommended that you use a virtual environment like homestead or similar. 

**If you don't have a php.ini file**

You need to add one. An easy way to do that is to use the available default. The command would look like this if you use a virtual environment:
```cp /etc/php.ini/default /etc/php.ini``` 

If you add it and don't have a virtual environment, you may be denied installation privileges unless you use sudo to install. The command would look like this: 
```sudo cp /etc/php.ini/default /etc/php.ini``` 

Then provide your credentials to complete installation. 

Next, you'll need to go into the file to modify it. If you're in a virtual environment, you won't need sudo, but otherwise you may need sudo included in the command to make the modifications. Type:
```sudo nano /etc/php.ini```

Leave sudo off for virtual environments, or if you're able to leave it off. Once in the php.ini file, you need to look for two variables: 
* upload_max_filesize
* post_max_size 

Don't make these too big, or it will cause you problems, but you can increase **upload_max_filesize** up to 20M and **post_max_size** can be increased to 21M. **post_max_size** is the size of your video file plus anything else you're sending in the form with the video. In our case, a caption, so not too much extra data. 

Save your file when you're done making the changes. 

## Set up .env file
You're going to use api.video, so you'll want to add your API key to your .env file. Open the file and where it says APP_APIVIDEO=yourkeyhere, remove yourkeyhere and put your key instead. You don't need to add quotes to show it's a string. You can find your API key in your dashboard here: https://my.api.video after you log in. If you need a new account, then click **Get Started** to sign up.

## What we'll be doing
The project is designed to teach you many of the key features of Laravel. It shows you how to store images, and then retrieve them with the help of an image repository and a database containing details about each image that can be used for retrieval. We are going to tweak things so that when you upload a video, it's sent to api.video. Then an embed link is stored in your database. This information is pulled from the database and displayed in your profile feed in an iframe. 

You'll need to have these things:

* api.video account
* api.video PHP client - [https://github.com/apivideo/php-api-client](https://github.com/apivideo/php-api-client)

The client can be installed by going into your project and typing the command:
```composer require api-video/php-api-client```

Make sure you also have the symfony http-client:
``` composer require symfony/http-client```

Run `composer update` to make sure everything ends up in your project.

You can then add the API as needed. We're going to modify the following files in the project: 

* PostsController.php
* posts/index.blade.php
* posts/show.blade.php
* profiles/index.blade.php

Everything is already set up for you in the repository. This walkthrough just shows you the modifications. The big change is setting things up so you can accept videos as well as images. It's limited to .mp4 and .mov files. The way the demo works before tweaks, is you upload an image and store it in storage/app/public. Then you reference it in a table in your database and retrieve images for displays as needed. 

We change things so that you can upload a video to api.video, then store a link to the mp4 in the database. When you retrieve a link, you'll check if it starts with http or not. If it doesn't, it's an image file in the storage/app/public folder. If it does, it's a video. 

What follows are the code samples for the different files. 

## PostsController.php
This controller handles everything to do with posts, from creating to displaying to storing them. We're going to modify the store() function. The code sample shows everything added into the file - you'll also need the rest of the file as it's set up. I've just pulled out the relevant section for our discussion.

Here, we're modifying the code for 'image'. We check 'image' to see if it has a .mp4 or .mov extension. If so, we run validation checking it that's to do with video. If everything checks out with the file, we send a request to api.video to upload a new video. We create a video container and upload our file into the container. Then we retrieve the embed link for the mp4 and send that path to be saved in the database for posts. Finally, we return the profile page, where the new post will be displayed. 

## posts/index.blade.php
For this section, inside the @foreach statement we update the display tags to handle image or video, depending on what we retrieve from our database.

Here we can see that if we have a link that starts 'http' we choose to display with an iframe because we know it will be a video. If we have a link that starts with anything else, we know it's an image and display with an image tag. 

## posts/show.blade.php
When we show a post, we want to make sure we display it with an iframe for a video, and an img tag for an image. 

Here, using an @if statement in blade, we set up a way to handle a post if it's video or if it's an image. Videos only use half the space of an image.

## profiles/index.blade.php
This is more of the same tweak. We want to be able to handle and display an image or a video properly. The code looks about the same:

## More tweaks 
There's a lot more you can add to this project. You can make it so you can navigate to your profile without having to know what number you are. You could consider learning to add a search bar, so you can hunt for users. You can add tagging and ways to display pictures that match certain tags. There's a lot of ways to build on what we have here, but this will get you started! 

thumbnail_apividstagram-1.png

apividstagram-1.png

Create your own version of Instagram using api.video and Laravel

Product updates

api.video is proud to announce a brand new PHP client for our video API. Our old PHP SDK will be deprecated. You can continue to use it, but it will no longer be updated. Instead, the new PHP client will stay up-to-date with all our new feature releases. 

Like our other clients, it's autogenerated and handles authentication for you, including refreshing your access token when needed. It also handles paginated responses and chunked uploads for large files. A unique aspect of this client is that it is also [PSR-18](https://www.php-fig.org/psr/psr-18/) compliant. This makes it more reusable as it reduces the number of dependencies and lowers the likelihood of version conflicts.

You can install our new client with:
```composer require api-video/php-api-client```

And the entire client is available in the GitHub repository here: 
[https://github.com/apivideo/php-api-client](https://github.com/apivideo/php-api-client)

In addition to the documentation we have at docs.api.video, you can find client-specific documentation in the GitHub repository. If you are looking up parameters, we recommend that you refer to the content provided in the client respository first. Some information may be tweaked to make it easier to create and use the client. There's a docs page for each part of the API here: [https://github.com/apivideo/php-api-client/tree/main/docs/Api](https://github.com/apivideo/php-api-client/tree/main/docs/Api) 

PHP is fast, flexible and widely used in web applications. We hope you'll enjoy using our new client to code your video projects! 



large_php.png

medium_php.png

small_php.png

thumbnail_php.png

php.png

api.video announces a new PHP client

Video update

This script is part of a collection of scripts from Hervé Pita that help with bulk video uploads. Everything is available in our [Helpful PHP Scripts](https://github.com/apivideo/helpful-scripts) repository on Github. In each part of this series, we'll walk through how to set up one of the scripts. What you'll find includes:

* [Ingest Videos from Google Drive](https://api.video/blog/tutorials/helpful-php-scripts-upload-videos-from-google-drive-to-api-video) - You can transfer all your videos from a folder in Google Drive to your api.video account with this CLI script.
* [Ingest Videos from an FTP Server](https://api.video/blog/tutorials/helpful-php-scripts-pt-2-upload-videos-from-an-ftp-server) - Transfer all your videos from the FTP server of your choice to your api.video account.
* [Export All Your Video Data to .csv](https://api.video/blog/tutorials/helpful-php-scripts-pt-3-export-all-your-video-details-to-a-csv) - With this script you can grab details about each video in your api.video account and gather it in one .csv spreadsheet.
* [Update Metadata for api.video Videos Using CSV](https://api.video/blog/tutorials/helpful-php-scripts-pt-4-update-metadata-for-api-video-videos-using-csv) - You can update your metadata in bulk with this script.
* [Update Video Settings in Bulk Without a CSV File](https://api.video/blog/tutorials/helpful-php-scripts-pt-5-bulk-update-without-a-csv-file) - Update videos to all be public or private or offer an mp4 download or disable an mp4 download.

Today we're going to learn how to use the script that lets you do a bulk update without a CSV file. Rather than choosing custom fields, these are preset. You'll be able to quickly update your videos to all:
* Be public 
* Be private
* Support an mp4 download
* Not support an mp4 download

## Prerequisites

For this project you'll need:

* PHP 5.4 or greater with the command-line interface (CLI) and JSON extension installed
* The [Composer](https://getcomposer.org/) dependency management tool (or another way to manage your dependency management). See the Composer website for installation options.
* A GitHub account
* An api.video [account](https://my.api.video)
* Your API key for either production or sandbox

## Installation

1. Navigate to the [Helpful PHP Scripts](https://github.com/apivideo/helpful-scripts) repository.
2. Click **Code** and from the drop-down click **Download ZIP**. (You can also install from the CLI if you prefer.)
3. Put the contents of your new .zip file in a folder you want to work from.
4. Navigate to the folder containing the contents of your zip file in the terminal.
5. In the terminal, type ```composer require api-video/php-sdk```

## Try the Script

1. In the terminal, type ```php bulk_scripts.php```
2. You're asked what environment you want to use, prod or sandbox (p or s). Choose **p**. 
3. Provide your API key. Make sure it matches the environment choice you made in the last step. You can get your key by navigating to [my.api.video](https://my.api.video) and copying the appropriate key.
4. Next, you choose what operation to apply to all your videos. The options are private - this makes all your videos private. public - this makes all your videos public. mp4on - this makes all videos offer an mp4 download. mp4off - this makes all videos disable the option of an mp4 download. 
5. The script runs and when it's done, you can check to see the settings are updated. If you made a mistake, you can bulk update again to correct, or if you need to change only some videos, try the script that lets you update some files that you list in a .tsv - [Update Metadata for api.video Videos Using CSV](https://api.video/blog/tutorials/helpful-php-scripts-pt-4-update-metadata-for-api-video-videos-using-csv)

And that's it for today! 

large_pat-whelen-xsswba4rb6e-unsplash.jpg

medium_pat-whelen-xsswba4rb6e-unsplash.jpg

small_pat-whelen-xsswba4rb6e-unsplash.jpg

thumbnail_pat-whelen-xsswba4rb6e-unsplash.jpg

pat-whelen-xsswba4rb6e-unsplash.jpg

Helpful PHP Scripts Pt 5: Update Video Settings in Bulk Without a CSV File

This script is part of a collection of scripts from Hervé Pita that help with bulk video uploads. Everything is available in our [Helpful PHP Scripts](https://github.com/apivideo/helpful-scripts) repository on Github. In each part of this series, we'll walk through how to set up one of the scripts. What you'll find includes:

* [Ingest Videos from Google Drive](https://api.video/blog/tutorials/helpful-php-scripts-upload-videos-from-google-drive-to-api-video) - You can transfer all your videos from a folder in Google Drive to your api.video account with this CLI script.
* [Ingest Videos from an FTP Server](https://api.video/blog/tutorials/helpful-php-scripts-pt-2-upload-videos-from-an-ftp-server) - Transfer all your videos from the FTP server of your choice to your api.video account.
* [Export All Your Video Data to .csv](https://api.video/blog/tutorials/helpful-php-scripts-pt-3-export-all-your-video-details-to-a-csv) - With this script you can grab details about each video in your api.video account and gather it in one .csv spreadsheet.
* [Update Metadata for api.video Videos Using CSV](https://api.video/blog/tutorials/helpful-php-scripts-pt-4-update-metadata-for-api-video-videos-using-csv) - You can update your metadata in bulk with this script.
* [Update Video Settings in Bulk Without a CSV File](https://api.video/blog/tutorials/helpful-php-scripts-pt-5-bulk-update-without-a-csv-file) - Update videos to all be public or private or offer an mp4 download or disable an mp4 download.

Today we're going to learn how to use the script for updating custom you choose using a CSV file. This will allow you to make updates in bulk, so be careful! With great power comes great responsibility. 

## Prerequisities

For this project you'll need:
* PHP 5.4 or greater with the command-line interface (CLI) and JSON extension installed
* The [Composer](https://getcomposer.org) dependency management tool (or another way to manage your dependency management). See the Composer website for installation options.
* A GitHub account
* An api.video [account](https://my.api.video)
* Your API key for either production or sandbox (the script will update video metadata based on your API key - if you choose production your production videos are updated, if you choose sandbox, your sandbox videos are updated)

## Installation

1. Navigate to the Helpful PHP Scripts repository.
2. Click **Code** and from the ddrop-down click **Download ZIP**. (You can also install from the CLI if you prefer.)
3. Put the contents of your new .zip file in a folder you want to work from.
4. Navigate to the folder containing the contents of your zip file in the terminal.
5. In the terminal, type: ```composer require api-video/php-sdk```

## Prepare Your .csv File 
You're going to need a .csv file containing the information you want to update. The script is designed to be flexible, so you can include any three fields for the columns after the first column, which you must label **id**. In this column you place your videoId. The script can handle legacy video IDs beginning 'vi' or the new ones beginning 'video_'. The next three columns can be the parameters you decide on. In this walkthrough, I picked **title**, **description**, and **public**. I can use these to set the title of my video, provide a description of the video, and choose whether it will be public or private. 

Make sure the top of your file has the field headings, and they correspond to exactly how they are presented in the api.video API. If you need a refresher, check out [docs.api.video](https://docs.api.video/reference) to make sure you're setting up your file correctly. 

Set up all the files you want to edit, one row per video file. Then save your file as **.csv** or **.tsv**. Hervé's script will accept either ending, but be aware that you MUST set up your file so that the separator is a tab, or the script won't run. The easiest way to do this is to save it as **.tsv**.

After you set up your file, place it in the same folder that you run your script from. The script will expect to be able to retrieve your file from this location. 

NOTE: Double and triple check your rows! You don't want to accidentally upload mistake updates if you don't have to. 

## Try the Script

1. In the terminal, type ```php update_metadata.php``` 
2. You're asked what environment you want to use, prod or sandbox. For our walkthrough, choose **prod**.
3. Provide your API key when prompted. You can get this by navigating to [my.api.video](https://my.api.video) and copying the appropriate key.
4. You're asked to provide the name of the file you want to use. Provide the full name of the file, including the ending. 
5. You're asked if you're ready to have your file checked to make sure it has the right headings. Put **y**.
6. If all goes well, the metadata you provided is added! Go check your videos to see if they list the information you wanted to provide. 

Thanks for checking out the latest installment of helpful PHP scripts for bulk video uploads! 

small_pexels-negative-space-34600.jpg

thumbnail_pexels-negative-space-34600.jpg

pexels-negative-space-34600.jpg

Helpful PHP Scripts Pt 4: Update Metadata for api.video Videos Using CSV

In our 3rd installment of helpful PHP scripts for bulk video uploads, we'll take a look at how to export all your video data to a .csv file. This script is part of a collection of scripts that help with bulk video uploads. All are available in our [Helpful PHP Scripts](https://github.com/apivideo/helpful-scripts) repository on GitHub. In each part of this series, we'll walk through how to set up one of them. The scripts you'll find include:

* [Ingest Videos from Google Drive](https://api.video/blog/tutorials/helpful-php-scripts-upload-videos-from-google-drive-to-api-video/) - You can transfer all your videos from a folder in Google Drive to your api.video account with this CLI script.
* [Ingest Videos from an FTP Server](https://api.video/blog/tutorials/helpful-php-scripts-pt-2-upload-videos-from-an-ftp-server/) - Transfer all your videos from the FTP server of your choice to your api.video account.
* [Export All Your Video Data to .csv](https://api.video/blog/tutorials/helpful-php-scripts-pt-3-export-all-your-video-details-to-a-csv/) - With this script you can grab details about each video in your api.video account and gather it in one .csv spreadsheet.
* [Update Metadata for api.video Videos Using CSV](https://api.video/blog/tutorials/helpful-php-scripts-pt-4-update-metadata-for-api-video-videos-using-csv/) - You can update your metadata in bulk with this script.
* [Update Video Settings in Bulk Without a CSV File](https://api.video/blog/tutorials/helpful-php-scripts-pt-5-bulk-update-without-a-csv-file/) - Update videos to all be public or private or offer an mp4 download or disable an mp4 download.

medium_pexels-negative-space-97077.jpg

small_pexels-negative-space-97077.jpg

thumbnail_pexels-negative-space-97077.jpg

pexels-negative-space-97077.jpg

We'll be talking about Export All Your Video Data to .csv today! You'll be able to see: 
* **videoId** - the unique identifier for referencing the video in API calls
* **title** - the title of the video
* **publishedAt** - when a video was published, in ISO-8601 format
* **iframe code** - the code for embedding your video as an iframe 
* **thumbnail** - the thumbnail image for the video if one was set 
* **mp4Support** - the URL for the mp4 of the video if one is available
* **metadata** - all key value pairs you set to describe the video (if you didn't set any you won't have them) 

You can check out the API reference documentation for listing videos, which is what we'll use to export our content to a .csv file. The API reference content is here: [List all videos](https://docs.api.video/reference/list-videos) 

You can use the videoId to associate the video with a custom player you created. 

Now that you know what kind of data you'll receive, let's get started! 

## Prerequisites

For this project you'll need:

* PHP 5.4 or greater with the command-line interface (CLI) and JSON extension installed
* The [Composer](https://getcomposer.org/) dependency management tool (or another way to manage your dependency management). See the Composer website for installation options.
* A GitHub account
* An api.video [account](https://dashboard.api.video/register)
* Your API key for either production or sandbox 

## Installation 

1. Navigate to the [Helpful PHP Scripts](https://github.com/apivideo/helpful-scripts) repository. 
2. Click **Code** and from the drop-down click **Download ZIP**. (You can also install from the CLI if you prefer.)
3. Put the contents of your new .zip file in a folder you want to work from.
4. Navigate to the folder containing the contents of your zip file in the terminal.
5. In the terminal, type: ```composer require api-video/php-sdk```

## Try the Script

1. In the terminal, type ```php create_csv.php```
2. You're asked what environment you want to use, prod or sandbox. For our walkthrough, choose **prod**. NOTE: You should choose the environment you have videos for. If you choose one of these environments and don't have videos stored there, you won't get any data to review.
3. Provide your API key. You can get this by navigating to [my.api.video](https://dashboard.api.video) and copying the appropriate key.
4. Your .csv file will build and be output to **project_details.csv**. 

You can also view the documentation for listing all videos in our API reference content here: [List all videos](https://docs.api.video/reference/list-videos)
Thanks for checking out our latest installment of Helpful PHP scripts! If you have any question or suggestions, please share them on our [community forum](https://community.api.video/). 


<a href="https://www.pexels.com/photo/office-working-app-computer-97077/">Photo by Negative Space from Pexels</a>

Helpful PHP scripts Pt. 3 - Export all your video details to a .csv file

We're back with more helpful PHP scripts from Hervé Pita! If you have video content on an FTP server, you can use this script to move your files from there to api.video. 

This script is part of a collection of scripts that help with bulk video uploads. Everything is available in our [Helpful PHP Scripts](https://github.com/apivideo/helpful-scripts) repository on Github. In each part of this series, we'll walk through how to set up one of the scripts. What you'll find includes:

* [Ingest Videos from Google Drive](https://api.video/blog/tutorials/helpful-php-scripts-upload-videos-from-google-drive-to-api-video) - You can transfer all your videos from a folder in Google Drive to your api.video account with this CLI script.
* [Ingest Videos from an FTP Server](https://api.video/blog/tutorials/helpful-php-scripts-pt-2-upload-videos-from-an-ftp-server) - Transfer all your videos from the FTP server of your choice to your api.video account.
* [Export All Your Video Data to .csv](https://api.video/blog/tutorials/helpful-php-scripts-pt-3-export-all-your-video-details-to-a-csv) - With this script you can grab details about each video in your api.video account and gather it in one .csv spreadsheet.
* [Update Metadata for api.video Videos Using CSV](https://api.video/blog/tutorials/helpful-php-scripts-pt-4-update-metadata-for-api-video-videos-using-csv) - You can update your metadata in bulk with this script.
* [Update Video Settings in Bulk Without a CSV File](https://api.video/blog/tutorials/helpful-php-scripts-pt-5-bulk-update-without-a-csv-file) - Update videos to all be public or private or offer an mp4 download or disable an mp4 download.

Today we're going to learn how to use the script for ingesting videos from an FTP server. Let's get started! 

## Prerequisites for Upload Videos from an FTP Server

For this project, you'll need to ensure that you have: 
* PHP 5.4 or greater with the command-line interface (CLI) and JSON extension installed
* The [Composer](https://getcomposer.org/) dependency management tool (or another way to manage your dependency management). See the Composer website for installation options.
* A GitHub account
* An Api.video account
* Your API key for either production or sandbox
* An FTP server account

You can also check out the API reference documentation for uploading a video here: [Upload a video](https://docs.api.video/reference/post_videos-videoid-source)

## Installation 

1. Navigate to the [Helpful PHP Scripts](https://github.com/apivideo/helpful-scripts) repository. 
2. Click **Code** and from the drop-down click **Download ZIP**. (You can also install from the CLI if you prefer.)
3. Put the contents of your new .zip file in a folder you want to work from.
4. Navigate to the folder containing the contents of your zip file in the terminal.
5. In the terminal, type: ```composer require api-video/php-sdk```

## Try the Script

1. Type ```php import_from_ftp.php``` 
2. You're asked what environment you want to use, prod or sandbox. For our walkthrough, choose **prod**. NOTE: Make sure you have the correct API key, they are different for production and sandbox. Production is better because there is no watermark across your videos. In sandbox mode, all transferred videos will say 'FOR DEVELOPMENT PURPOSES ONLY' across them.
3. You're asked to provide your API key, go ahead and paste in your Production API key. If you weren't sure where to get it from, navigate to [my.api.video](https://my.api.video) and grab the key from the Production section on the Overview page.
4. If authentication is successful, you are next asked if you want to associate a playerID with your videos. You can customise and brand players, then associate them with videos if you like. (View a tutorial about [video player customisation here](https://api.video/blog/tutorials/tutorial-video-player-customisation).) For the sake of simplicity, we'll skip this. Type **n**.
5. Now you're asked to provide the address for your FTP server. Type the complete address, exactly as it appears, or paste it in. 
6. Enter your FTP username.
7. Enter your FTP password.
8. Provide the path to the video folder on your FTP server that you want to use for the transfer.
9. The script will now step through all your files and upload any videos it finds to api.video. You receive a note after each file is successfully written to api.video. 

That's all for this installment of helpful PHP scripts! More to come! 

<a href="https://www.pexels.com/photo/black-laptop-computer-turned-on-showing-computer-codes-177598/">Photo by Markus Spiske from Pexels</a>

medium_php.jpg

small_php.jpg

thumbnail_php.jpg

php.jpg

Helpful PHP Scripts Pt 2 - Upload Videos from an FTP Server

Featured article

# api.video blog

Blog

Follow the api.video Blog to explore tutorials, video use cases, and learn about on-demand and live-streaming video updates.