- Get Started
- Help
- Troubleshooting
- Installation
- Authentication/Access Tokens
- Make requests
- Upload videos from a server
- Replace videos from a server
- Client side uploads
- Upload videos from a URL
- Upload images
- Framework Integrations
There is a lot of information about the Vimeo API at https://developer.vimeo.com/api/start. Most of your questions will be answered there!
The API docs often uses dot notation to represent a hierarchy of data (eg. privacy.view). Because this library sends all data using JSON, you must use nested associative arrays, not dot notation.
// The docs refer to the following as "privacy.view"
array('privacy' => array('view' => 'disable'));
- Require this package, with Composer, in the root directory of your project.
composer require vimeo/vimeo-api
- Use the library
$lib = new \Vimeo\Vimeo($client_id, $client_secret)
- Download the latest release : v1.3.0
- Include the autoloader
require("/path/to/vimeo.php/autoload.php");
- Use the library
$lib = new \Vimeo\Vimeo($client_id, $client_secret)
All requests require access tokens. There are two types of access tokens.
- Unauthenticated - Access tokens without a user. These tokens can only view public data
- Authenticated - Access tokens with a user. These tokens interact on behalf of the authenticated user.
Unauthenticated API requests must generate an access token. You should not generate a new access token for each request, you should request an access token once and use it forever.
// scope is an array of permissions your token needs to access. You can read more at https://developer.vimeo.com/api/authentication#supported-scopes
$token = $lib->clientCredentials(scope);
// usable access token
var_dump($token['body']['access_token']);
// accepted scopes
var_dump($token['body']['scope']);
// use the token
$lib->setToken($token['body']['access_token']);
- Build a link to Vimeo so your users can authorize your app.
$url = $lib->buildAuthorizationEndpoint($redirect_uri, $scopes, $state)
Name | Type | Description |
---|---|---|
redirect_uri | string | The uri the user is redirected to in step 3. This value must be provided to every step of the authorization process including creating your app, building your authorization endpoint and exchanging your authorization code for an access token. |
scope | array | An array of permissions your token needs to access. You can read more at https://developer.vimeo.com/api/authentication#scopes. |
state | string | A value unique to this authorization request. You should generate it randomly, and validate it in step 3. |
-
Your user will need to access the authorization endpoint (either by clicking the link or through a redirect). On the authorization endpoint the user will have the option to deny your app any scopes you have requested. If they deny your app, they will be redirected back to your redirect_url with an
error
parameter. -
If the user accepts your app, they will be redirected back to your redirect_uri with a
code
andstate
query parameter (eg. http://yourredirect.com?code=abc&state=xyz).- You must validate that the
state
matches your state from step 1. - If the state is valid, you can exchange your code and redirect_uri for an access token.
- You must validate that the
// redirect_uri must be provided, and must match your configured uri
$token = $lib->accessToken(code, redirect_uri);
// usable access token
var_dump($token['body']['access_token']);
// accepted scopes
var_dump($token['body']['scope']);
// use the token
$lib->setToken($token['body']['access_token']);
For additional information, check out the example
The API library has a request
method which takes three parameters. It returns an associative array containing all of the relvant request information.
Usage
Name | Type | Description |
---|---|---|
url | string | The URL path (e.g.: /users/dashron ). |
params | string | An object containing all of your parameters (e.g.: { "per_page": 5, "filter" : "featured"} ). |
method | string | The HTTP method (e.g.: GET ). |
$response = $lib->request('/me/videos', array('per_page' => 2), 'GET');
Response
The response array will contain three keys.
Name | Type | Description |
---|---|---|
body | assoc array | The parsed request body. All responses are JSON so we parse this for you, and give you the result. |
status | number | The HTTP status code of the response. This partially informs you about the success of your API request. |
headers | assoc array | An associative array containing all of the response headers. |
$response = $lib->request('/me/videos', array('per_page' => 2), 'GET');
var_dump($response['body']);
To upload videos you must call the upload
method. It accepts two parameters. It will return the URI of the new video.
For more information check out the example
Name | Type | Description |
---|---|---|
file | string | Full path to the upload file on the local system. |
$response = $lib->upload('/home/aaron/Downloads/ada.mp4')
To replace the source file of a video, you must call the replace
method. It accepts three parameters. It will return the URI of the replaced video.
Name | Type | Description |
---|---|---|
video_uri | string | The URI of the original video. Once uploaded and successfully transcoded your source video file will be swapped with this new video file. |
file | string | Full path to the upload file on the local system. |
$response = $lib->replace('/videos/12345', '/home/aaron/Downloads/ada.mp4')
To upload from the client, you will have to mix some server side, and client side API requests. We support two workflows, the first of which is much easier than the second.
This workflow is well documented on Vimeo's developer site. You can read more here: https://developer.vimeo.com/api/upload#simple-http-post-uploading
Streaming uploads support progress bars, and resumable uploading. If you want to perform these uploads client side you will need to start with some server side requests.
Read through the Vimeo documentation first. Step 1 and 4 should be performed on the server, while step 2 and 3 can be performed on the client. With this workflow the video will never be transferred to your servers.
Uploading videos from a public url (also called "pull uploads") uses a single, simple API call.
$video_response = $lib->request('/me/videos', array('type' => 'pull', 'link' => $url), 'POST');
To upload an image, call the uploadImage
method. It takes three parameters.
For more information check out the example
Name | Type | Description |
---|---|---|
pictures_uri | string | The URI to the pictures collection for a single resource. eg. /videos/12345/pictures . You can always find this in the resource representation. |
file | string | Full path to the upload file on the local system. |
activate | boolean | (Optional) Defaults to false. If true this picture will become the default picture for the associated resource. |
$response = $lib->uploadImage('/videos/12345/pictures', '/home/aaron/Downloads/ada.png', true)
We are not aware of any issues with the latest version (1.3.0). If you have any questions or problems, create a ticket or contact us
- WordPress - http://vimeography.com/
- Laravel - https://github.com/vinkla/vimeo
If you have integrated Vimeo into a popular PHP framework let us know!
To see the contributors please visit the contributors graph.