canonical: https://jentic.com/apis/traileraddict.com/traileraddict

# TrailerAddict API

Easily embed trailers from TrailerAddict. Provides access to movie trailer data including searching for trailers, fetching embed codes, and browsing featured and recently added trailers. The API exposes 6 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get trailer by imdb id, get trailer by traileraddict film id. Covers 6 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get trailer by IMDB ID
- Search for trailers
- Integrate TrailerAddict API into automated workflows
- Query and filter TrailerAddict API records by parameters
- Monitor TrailerAddict API operational status and events

## Use cases

### Developer Tools Operations

Use the TrailerAddict API to perform developer tools operations programmatically. The API provides 6 endpoints covering core functionality including get trailer by imdb id, get trailer by traileraddict film id, search for trailers.

Example prompt: Call GET `/trailer/{imdbId}` to get trailer by imdb id

### Automated Trailers Management

Automate trailers operations by combining multiple TrailerAddict API endpoints. Agents can get trailer by traileraddict film id and then search for trailers in a single workflow.

Example prompt: Call GET `/trailer/{filmId}` to get trailer by traileraddict film id, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TrailerAddict API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get trailer by imdb id', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/trailer/{imdbId}` | Get trailer by IMDB ID |
| GET | `/trailer/{filmId}` | Get trailer by TrailerAddict film ID |
| GET | `/search` | Search for trailers |
| GET | `/featured` | Get featured trailers |
| GET | `/just-added` | Get recently added trailers |
| GET | `/film/{filmId}` | Get film information |

## Key resources

- **Trailers** — Trailer lookup and search operations
- **Films** — Film information and browsing
- **Featured** — Featured and popular trailers

## Why Jentic

- **Setup:** Wiring the TrailerAddict API by hand means passing its apikey as a query parameter on every call to api.traileraddict.com and handling error responses yourself. Through Jentic you install once, import the TrailerAddict API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The TrailerAddict API is read-only, so scope the agent to the operations it needs, such as fetching a trailer by film id or searching, and leave out anything the workflow does not require. Every operation you allow is one you have chosen.
- **Credential handling:** Your TrailerAddict API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get a trailer by imdb id' or 'search for a film trailer', and Jentic returns the matching TrailerAddict API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the TrailerAddict API use?

The TrailerAddict API uses an API key passed in the `apikey` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get trailer by imdb id with the TrailerAddict API?

Yes. Use the GET `/trailer/{imdbId}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the TrailerAddict API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get trailer by imdb id through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get trailer by imdb id'. Jentic returns the matching TrailerAddict API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the TrailerAddict API have?

The TrailerAddict API exposes 6 endpoints covering trailers, films, featured operations.

### Can I limit what my agent is allowed to do with the TrailerAddict API?

Yes. Jentic One runs self-hosted, so you set the rules that decide which TrailerAddict API operations and credentials your agent may use. The TrailerAddict API is read-only, so you can allow just the operations a workflow needs, such as getting a trailer by IMDB ID or film ID, searching for trailers, or listing featured and recently added trailers, and leave out the rest. Every operation the agent can call is one you have chosen to permit.