canonical: https://jentic.com/apis/Sonarr/sonarr

# Sonarr

Sonarr API docs - The v3 API docs apply to both v3 and v4 versions of Sonarr. Some functionality may only be available in v4 of the Sonarr application. The API exposes 234 endpoints secured with apiKey authentication.

## For AI agents

Programmatically access Sonarr resources. Covers 234 operations with apiKey authentication.

## Scope

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

## Capabilities

- Access Sonarr resources via REST API
- Manage developer tools data programmatically
- Integrate Sonarr into automated workflows
- Query and filter Sonarr records by parameters
- Monitor Sonarr operational status and events

## Use cases

### Developer Tools Operations

The API provides 234 endpoints for developer tools operations.

Example prompt: Execute a primary operation against the Sonarr

### Data Retrieval and Monitoring

Query Sonarr resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Sonarr endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Sonarr 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 'sonarr', load the operation schema, and execute with Jentic-managed credentials

## Key resources

- **Autotagging** — Operations for autotagging
- **Blocklist** — Operations for blocklist
- **Calendar** — Operations for calendar
- **Command** — Operations for command
- **Config** — Operations for config

## Why Jentic

- **Setup:** Wiring Sonarr by hand means managing its API key and pointing at your self-hosted instance's protocol and host yourself. Through Jentic you install once, import Sonarr from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Sonarr uses a single API key across its operations, so limit the agent to the operations it needs, such as reading your series library, and leave out state-changing calls like adding or deleting series unless you add them. You choose the allowed set, so only the operations you pick can run.
- **Credential handling:** Your Sonarr 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 'list series in Sonarr' or 'add a series to Sonarr', and Jentic returns the matching Sonarr 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 Sonarr use?

The Sonarr uses an API key passed in the `X-Api-Key` header. 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.

### What are the rate limits for the Sonarr?

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 use sonarr through Jentic?

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

### How many endpoints does the Sonarr have?

The Sonarr exposes 234 endpoints covering autotagging, blocklist, calendar operations.

### Does the Sonarr support pagination?

Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.

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

Yes. Because Sonarr uses a single API key across all of its operations, Jentic One, which you self-host, lets you decide which operations that key is allowed to run. You can restrict the agent to read-only calls such as listing your series library or checking the calendar, and leave out state-changing operations like adding or deleting series unless you choose to include them. Only the operations you select can be called, so your own rules govern what the agent can do.