canonical: https://jentic.com/apis/trakt.tv/trakt-api

# Trakt Tv Trakt API

At Trakt, we collect lots of interesting information about what tv shows and movies everyone is watching. Part of the fun with such data is making it available for anyone to mash up and use on their own site or app. The Trakt API was made just for this purpose. It is very easy to use, you basically call a URL and get some JSON back. More complex API calls (such as adding a movie or show to your co. The API exposes 183 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically get dvd releases, get movies. Covers 183 operations with oauth2 authentication.

## Scope

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

## Capabilities

- Get DVD releases
- Manage communications data programmatically
- Integrate Trakt API into automated workflows
- Query and filter Trakt API records by parameters
- Monitor Trakt API operational status and events

## Use cases

### Communications Operations

Use the Trakt API to perform communications operations programmatically. The API provides 183 endpoints covering core functionality including get dvd releases, get movies, get new shows.

Example prompt: Call GET /calendars/all/dvd/{start_date}/{days} to get dvd releases

### Automated Authentication - OAuth Management

Automate authentication - oauth operations by combining multiple Trakt API endpoints. Agents can get movies and then get new shows in a single workflow.

Example prompt: Call GET /calendars/all/movies/{start_date}/{days} to get movies, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Trakt 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 oauth2 tokens manually.

Example prompt: Search Jentic for 'get dvd releases', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /calendars/all/dvd/{start_date}/{days} | Get DVD releases |
| GET | /calendars/all/movies/{start_date}/{days} | Get movies |
| GET | /calendars/all/shows/new/{start_date}/{days} | Get new shows |
| GET | /calendars/all/shows/premieres/{start_date}/{days} | Get season premieres |
| GET | /calendars/all/shows/{start_date}/{days} | Get shows |
| GET | /calendars/my/dvd/{start_date}/{days} | Get DVD releases |
| GET | /calendars/my/movies/{start_date}/{days} | Get movies |
| GET | /calendars/my/shows/new/{start_date}/{days} | Get new shows |

## Key resources

- **Authentication - OAuth** — The API uses OAuth2.  If you know what's up with OAuth2, grab your library and starting rolling. If
- **Authentication - Devices** — Device authentication is for apps and services with limited input or display capabilities. This incl
- **Calendars** — By default, the calendar will return all shows or movies for the specified time period and can be gl
- **Checkin** — Checking in is a manual action used by mobile apps allowing the user to indicate what they are watch
- **Certifications** — Operations related to Certifications

## Why Jentic

- **Setup:** Wiring the Trakt API by hand means running its OAuth2 authorization-code flow, refreshing tokens, and handling errors against api.trakt.tv yourself. Through Jentic you install once, import the Trakt API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** The Trakt calendar operations key off the authenticated user rather than a resource id in the URL path, so scope the agent to the operations it needs, such as reading all-DVD or all-movie releases, and leave out personal calendar reads unless the workflow requires them. Every operation you allow is one you have chosen.
- **Credential handling:** Your Trakt OAuth2 credential 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 upcoming DVD releases' or 'list new show premieres', and Jentic returns the matching Trakt API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Trakt API use?

The Trakt API uses OAuth 2.0 for authorization. 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 dvd releases with the Trakt API?

Yes. Use the GET /calendars/all/dvd/{start_date}/{days} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Trakt 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 dvd releases through Jentic?

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

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

The Trakt API exposes 183 endpoints covering authentication - oauth, authentication - devices, calendars operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Trakt operations and credentials the agent may use. Since the Trakt calendar operations key off the authenticated user rather than a resource id in the path, you allow only the endpoints the workflow needs, such as reading all-DVD releases at GET /calendars/all/dvd/{start_date}/{days} or all-movie releases at GET /calendars/all/movies/{start_date}/{days}. You can leave out the personal calendar reads under /calendars/my/ unless a task requires them, so every operation the agent can call is one you have chosen.