310b518ece
* Init: New Source: TMDb * chore: Added documentation * Chore: All Comments Resolved * Added language config for filtering, All comomments resolved * Update Doc URL * add tmdb to source def and format files * Removed unwanted authenticator, Added request params and configs * cleansed lint * feat: Added pagination, refactor: moved example to spec.yaml and minor corrections * fix: change required in spec.yaml, corrections to docs * removed unwanted file change * remove movies_changes * auto-bump connector version Co-authored-by: btkcodedev <btk.codedev@gmail.com> Co-authored-by: marcosmarxm <marcosmarxm@gmail.com> Co-authored-by: Marcos Marx <marcosmarxm@users.noreply.github.com> Co-authored-by: Octavia Squidington III <octavia-squidington-iii@users.noreply.github.com>
1.1 KiB
1.1 KiB
TMDb
The connector uses the v3 API documented here: https://developers.themoviedb.org/3/getting-started/introduction. It is straightforward HTTP REST API with API Authentication.
API key
Api key is mandate for this connector to work. It could be generated using a free account at TMDb. Visit: https://www.themoviedb.org/settings/api
Implementation details
Setup guide
Step 1: Set up TMDb connection
- Have an API key by generating personal API key (Example: 12345)
- A movie ID, or query could be configured in config.json (Not Mandate, Default movie _id would be 550 and query would be marvel)
- See sample_config.json for more details
Step 2: Generate schema for the endpoint
Custom schema is generated and tested with different IDs
Step 3: Spec, Secrets, and connector yaml files are configured with reference to the Airbyte documentation.
In a nutshell:
- Navigate to the Airbyte Open Source dashboard.
- Set the name for your source.
- Enter your
api_key. - Enter params
movie_id, query, language(if needed). - Click Set up source.
- We use only GET methods, all streams are straightforward.