TMDB to MySQL: How to Move Your Data

Moving TMDB into MySQL sounds like building a film database, and it is worth understanding what this connector actually does before you scope a project that way. It is parameterised rather than bulk: you configure a specific movie ID and a specific search query, and the streams return data for those.

That makes it a good fit for enriching records you already have, and a poor fit for replicating the catalogue. This guide covers the managed path with Airbyte, what the configuration implies, and when you should reach for something else instead.

TMDB to MySQL at a glance:

Why move data from TMDB to MySQL?

One situation fits this connector well and one does not, and the difference is worth establishing before anything else.

It fits enrichment and exploration. You have an application whose database holds titles, and you want TMDB's metadata for specific ones: runtime, genres, cast, ratings. Or you are prototyping and want a specific film's data in a table so you can see its shape before building anything larger.

It does not fit building a catalogue. Because the movie ID is a configuration field on the source rather than something iterated over, replicating thousands of films would mean thousands of source configurations. If that is your goal, define your own connector in Connector Builder against the TMDB API, where you can page through discovery endpoints properly.

What do you need before you start?

A short list, and one of these is a legal question rather than a technical one:

A TMDB API key. Created from your account settings on themoviedb.org. The TMDb source documentation covers the configuration fields.

A specific movie ID, and a specific search query. The movie ID is mandatory for the movie streams and the query is mandatory for the search streams, both entered when you create the source. Decide what they are before you start, because they define what this pipeline returns.

A language code. Expressed in the ISO 639-1 scheme, such as en-US, and mandatory for some streams. It also determines which localised titles and descriptions you receive, so it is a content decision as much as a configuration one.

A view on TMDB's terms of use. TMDB is a community-built database with its own conditions on how the data may be used and attributed. Storing it in your own systems and putting it in front of users is a licensing question worth answering before you build, not after.

On the destination side you need a MySQL database and a user able to create and write tables in the target schema. Volume is never a concern on this pipeline, which is a consequence of the scope rather than a virtue.

How do you build a TMDB to MySQL pipeline in Airbyte?

Step 1: Confirm this connector matches your goal

Write down what you expect in MySQL when this is finished. If the answer is one film's details, or the results of one search, this connector does that directly. If the answer is a table of every film in a genre, stop here and use Connector Builder instead, because no amount of configuration turns a per-movie source into a catalogue extract.

Step 2: Configure the TMDB source

Click Sources in the left navigation, then New Source, and select TMDb, following adding a source. Enter the API key, then the movie ID, query and language parameters as needed for the streams you intend to select. The connector uses TMDB's v3 API by default.

Step 3: Configure the MySQL destination

Click Destinations, then New Destination, and select MySQL, following adding a destination. Supply the host, port, database and credentials. Point it at a schema dedicated to reference data rather than one your application writes to, so the pipeline cannot collide with application tables.

Step 4: Select streams and schedule infrequently

Click Connections, then New connection, select the streams matching the parameters you supplied, and choose a sync mode. Film metadata changes rarely, so a daily or weekly schedule is generous. There is no benefit to syncing often, and TMDB is a community-run service whose API you should treat considerately.

Check the resulting tables after the first sync. Because the parameters are mandatory only for certain streams, selecting a stream whose parameter you did not supply produces confusing results rather than a clear error.

Why is the movie ID a configuration field?

Because the connector maps TMDB's per-resource endpoints directly. TMDB's API exposes details for a given film at a given identifier, and this connector asks you which identifier rather than iterating over a set. The same applies to search, where the query string is part of the source configuration rather than a parameter you vary.

That is a legitimate design for a connector whose job is retrieving specific things. It is simply not the design people expect from the phrase moving TMDB into a database, and the mismatch is the single most likely reason a project built on this disappoints.

If you need many films, the sensible route is Connector Builder against the TMDB API, defining a stream over a discovery or list endpoint with pagination configured properly. That is an afternoon of work and gives you something that scales, and it is covered in the REST API guides in this series.

What should you check before relying on this?

This is a community connector, and its documentation page carries some evident copy and paste from another connector's setup guide, referring to a different source by name in the middle of the instructions. That is a small thing and it is a fair signal about how closely the page has been maintained.

Practically, that means validating rather than assuming. Run a sync, look at the tables, and confirm the fields you need are present and populated before anything downstream depends on them. That advice applies to any community connector and rather more to one whose documentation has visible errors.

Note also that the connector defaults to TMDB's v3 API, with v4 described as in development. If your requirements depend on something only available in a newer API version, check the current state of both the TMDB API and this connector before planning around it.

Frequently asked questions

Can I replicate the whole TMDB catalogue with this connector?

No. The movie ID is a configuration field on the source, so the movie streams return data for that one film. For many films, build a connector in Connector Builder against TMDB's discovery endpoints instead.

Which parameters do I have to supply?

The API key always, a movie ID for the movie streams, a query for the search streams, and a language code for streams that require it. Selecting a stream without its parameter produces confusing output rather than a clear error.

Which TMDB API version does the connector use?

Version 3 by default. TMDB's v4 was described as in development, so check the current state of both if you need something newer.

Can I use TMDB data in my product?

That depends on TMDB's terms of use, which set conditions on how the data may be used and attributed. Check them before building rather than after.

Can I do this without writing code?

Yes for this connector, which is entirely UI-driven. If you move to Connector Builder for a catalogue extract, that is also a user interface rather than code.

Get your TMDB data into MySQL

Decide first whether you want a specific film or a catalogue, because this connector does the first and not the second. If it is the first, supply the parameters, schedule infrequently, validate the output, and check TMDB's terms. If it is the second, Connector Builder is the right tool and the switch is cheaper made now than later.

Airbyte's connector catalog includes 600+ pre-built connectors, and where none fits you can define your own. For that approach, see REST API to MySQL, and for the same technique pointed at a warehouse, REST API to Snowflake.

Start syncing now →