IMVDb is proud to announce that we're partnering with the Los Angeles Music Video Festival this year (Oct 1-7, 2017). Call for Entries is now open! Accepting submissions now through July 15!

Submit Here


IMVDb Data API Beta

The IMVDb Data API allows you to pull data from IMVDb and use it in your application. Before you get started, please read over this guidelines document which covers the basics of using the API.

Note: The API is in beta right now and is not recommended for use in production applications yet. Please follow @imvdbdev and check out the changelog for information on when the API reaches v1.0.

Registering Your App

Before you can start using the API, you'll need to get an app key by registering your application with us. It's quick and easy!

Register New App

Rate Limits

API calls are limited to 1,000 calls per minute. If you need a higher rate limit, please contact us. However, caching is preferrable over raising rate limits.

Acceptable Usage

You can use IMVDb's data for whatever you'd like in your application, as long as you do not use the data to simply build another music video database. No attribution is needed, but if you'd like to provide attribution, you can either provide a link or use one our downloadable brand assets to show the IMVDb logo.

Developer Support

The IMVDb Data API is currently and Beta and we want to hear about your issues and your feedback! Please post a message in our developer support section. We also have an email address posted if you have an issue that you want addressed privately.

Making API Calls

All API calls are made to the IMVDb API endpoint:

Note the v1 in the URL - right now the API is brand new so there is only one version, but as we might change the versions in the future, we are adding some versioning into the URI from the get-go.

API Headers

Here are the following headers you can send to the API. Note that only the API Key is required.


Your App key that you receive after registering your app. This is required or else your request will be returned with a 403 error.

IMVDB-APP-KEY: {Your App Key}


By default, API results are returned as JSON, but you can also specify XML, JSONP, or PHP Serialized as the response format using the Accept header.

Accept: application/json
Accept: application/xml
Accept: application/javascript
Accept: application/vnd.php.serialized

HTTP Status Codes

The API returns the following API status codes:

Code Description
200 OK
403 Forbidden (Returned when no API key or an invalid API key is sent)
404 Not found
500 Internal Server Error


In the event that you receive a status code that indicates an error, the API will return an error string like so:

    "status": false,
    "error": "Invalid API Key."

Testing API Calls

You can play around with the API using the API Sandbox. This allows you to try out requests without needing to get an app key.