connector-tmdb

# Movie and TV data with `tmdb-client` Motoko bindings for [The Movie Database API](https://developer.themoviedb.org/), generated from TMDb's OpenAPI spec. **124 operations in one module** (`Apis/DefaultApi`) — the spec carries no tags, so there is nothing to split on and no nested facade. **Read this before planning the app: the read surface works, the write surface does not.** Of the 124 operations, **111 are usable** and **13 are broken**: - **12** carry a request body — 11 of the 12 POSTs plus `authenticationDeleteSession` — and go out double-wrapped (§6). - **1** read, `movieRecommendations`, throws on every successful response (§6). Plan features around catalog reads (search, details, trending, discover, now-playing) and keep favorites, ratings and watchlists out of scope unless you are prepared to fix the generator first. Use `tvSeriesRecommendations` if you need a "more like this" row; its movie counterpart is the broken one. # Backend ## 1. Add the dependency ```bash mops add tmdb-client ``` ## 2. The credential **Use the v4 read-access token and `?#bearer`. That is the only credential this client supports.** ```mo:tmdb-client auth = ?#bearer "eyJhbGciOi…" // v4 read-access token, themoviedb.org/settings/api ``` TMDb also issues a v3 API key (32 hex chars) that normally travels as an `?api_key=…` query parameter. **This client cannot send it.** The spec declares exactly one security scheme — `apiKey` in a *header* named `Authorization`, tagged `x-beare...