# Listen Notes AI integration on Definable

> Listen Notes is a powerful podcast search engine and database that allows you to discover, explore, and listen to millions of podcasts and episodes worldwide.

## What this connects

Listen Notes is a powerful podcast search engine and database that allows you to discover, explore, and listen to millions of podcasts and episodes worldwide.

Vendor: https://www.listennotes.com

## Tools available

**26** tools available. First 12:

- `LISTENNOTES_BATCH_FETCH_BASIC_META_DATA_FOR_EPISODES` — Post episodes by ids — The listennotestest_episodes_post endpoint allows users to retrieve metadata for multiple podcast episodes in a single request. This POST endpoint accepts a list of episode IDs and returns detailed information about each specified episode. It's particularly useful for bulk retrieval of episode data, reducing the number of API calls needed when working with multiple episodes. The endpoint should be used when you need to fetch information about specific, known episodes rather than searching or browsing. Keep in mind that this endpoint is focused on retrieval only and does not support creating, updating, or deleting episode data.
- `LISTENNOTES_BATCH_FETCH_BASIC_META_DATA_FOR_PODCASTS` — Create podcast via form data — The listennotestest_podcasts_post endpoint allows users to retrieve information about multiple podcasts using various identifiers such as Listen Notes IDs, RSS feed URLs, Apple Podcasts IDs, or Spotify IDs. It can optionally fetch the latest episodes for the specified podcasts. This endpoint is useful for bulk podcast data retrieval and for staying updated on recent episodes across multiple shows. It's particularly valuable for applications that need to sync or update podcast information from different platforms. The endpoint has a limit of returning up to 15 latest episodes per request, so for comprehensive episode history, multiple calls may be necessary.
- `LISTENNOTES_FETCH_A_CURATED_LIST_OF_PODCASTS_BY_ID` — Retrieve curated podcast by id — Retrieves detailed information about a specific curated podcast using its unique identifier. This endpoint allows users to access comprehensive data about a carefully selected podcast collection, including its contents, curator information, and associated metadata. It's particularly useful for applications that want to display or analyze curated podcast lists. The endpoint should be used when detailed information about a known curated podcast is required, but it won't provide a list of all available curated podcasts or allow modifications to the curated content.
- `LISTENNOTES_FETCH_A_LIST_OF_BEST_PODCASTS_BY_GENRE` — Fetch best podcasts list — The getBestPodcasts endpoint retrieves a curated list of the best podcasts from the Listen Notes platform. It allows users to access a collection of top-rated or popular podcasts, which can be filtered by genre, region, and content rating. This endpoint is useful for discovering high-quality podcast content, creating recommendation systems, or populating podcast directories. The results are paginated for efficient data retrieval and can be customized to exclude explicit content if required. While it provides a valuable overview of top podcasts, it may not include real-time updates or notifications about new episodes or changes in podcast rankings.
- `LISTENNOTES_FETCH_A_LIST_OF_PODCAST_GENRES` — Retrieve genre list — The GetGenres endpoint retrieves a comprehensive list of available genres within the listennotestest platform. This endpoint is designed to provide users with up-to-date information on content categories, which can be used for filtering, organizing, or subscribing to specific types of content. It's particularly useful for applications that need to populate genre-based dropdown menus, create content recommendation systems, or set up genre-specific notification preferences. The endpoint does not require any input parameters, making it simple to use for fetching the entire genre catalog. However, users should be aware that the response may contain a large amount of data, depending on the number of genres available in the system.
- `LISTENNOTES_FETCH_A_LIST_OF_YOUR_PLAYLISTS` — Get playlists — Retrieves a list of playlists from the Listen Notes platform. This endpoint allows users to fetch all available playlists associated with their account or publicly accessible playlists. It should be used when you need to display a collection of playlists, such as in a user's library or for browsing purposes. The endpoint returns basic information about each playlist, which may include the playlist name, creator, number of episodes, and other relevant metadata. Note that this endpoint likely returns a limited number of playlists per request, and pagination might be necessary for retrieving large collections. It does not provide detailed information about the episodes within each playlist; separate API calls would be required to fetch that level of detail.
- `LISTENNOTES_FETCH_A_RANDOM_PODCAST_EPISODE` — Listen to just listen endpoint — The 'just_listen' endpoint is a basic listener or health check mechanism for the listennotestest app. It allows users to verify the availability and responsiveness of the service without requiring any input parameters. This endpoint should be used for monitoring the status of the listennotestest service or as a simple ping to ensure the API is operational. It's important to note that this endpoint likely doesn't provide any specific data about podcasts or user accounts. The response is expected to be minimal, possibly just confirming that the service is up and running. While useful for basic health checks, it should not be relied upon for any complex operations or data retrieval within the listennotestest ecosystem.
- `LISTENNOTES_FETCH_AUDIENCE_DEMOGRAPHICS_FOR_A_PODCAST` — Get podcast audience by id — Retrieves audience information for a specific podcast identified by its unique ID. This endpoint allows users to access demographic data, listening statistics, or other audience-related metrics for a particular podcast. It's useful for podcast creators, marketers, or analysts who want to understand their audience better or track the performance of their content. The tool returns aggregated data about the podcast's listeners, which may include but is not limited to age groups, geographic distribution, listening habits, or engagement metrics. It should be used when detailed audience insights for a specific podcast are needed. Note that this endpoint does not provide real-time listener counts or individual listener data to protect user privacy.
- `LISTENNOTES_FETCH_CURATED_LISTS_OF_PODCASTS` — Get curated podcasts — Retrieves a list of curated podcasts from the Listen Notes platform. This endpoint provides access to a collection of handpicked and organized podcasts, likely curated by experts or algorithms. It's useful for discovering high-quality content or featuring recommended podcasts to users. The endpoint returns a selection of podcasts, possibly grouped by themes, genres, or other criteria. While it offers a curated selection, it may not provide exhaustive search capabilities or personalized recommendations based on individual user preferences.
- `LISTENNOTES_FETCH_DETAILED_META_DATA_FOR_AN_EPISODE_BY_ID` — Retrieve episode by id — Retrieves detailed information about a specific episode using its unique identifier. This endpoint allows users to access comprehensive data about an individual episode, which may include metadata such as title, description, publication date, duration, and associated podcast information. It's particularly useful when you need to display or process information about a single episode. The endpoint should be used when detailed information about a known episode is required, but it won't provide lists of episodes or search functionality. Note that the response structure and the exact fields returned are not specified in the given schema, so the actual content may vary based on the API implementation.
- `LISTENNOTES_FETCH_PODCAST_EPISODES_BY_ID` — Fetch Podcast Details And Episodes — Retrieves detailed information about a specific podcast using its unique identifier. This endpoint allows users to fetch comprehensive data about a particular podcast, including but not limited to its title, description, author, episode list, and other metadata. It's ideal for applications that need to display in-depth information about a single podcast or integrate podcast data into their systems. The endpoint should be used when detailed information about a known podcast is required, rather than for searching or browsing multiple podcasts. Note that this endpoint only provides information for podcasts that exist within the Listen Notes database and may not include real-time updates for very recent changes to the podcast.
- `LISTENNOTES_FETCH_PODCAST_LANGUAGES` — Fetch podcast languages — Retrieves a list of supported languages in the Listen Notes API. This endpoint provides information about the languages available for use within the platform, which can be crucial for internationalization and localization efforts. Use this endpoint when you need to know which languages are supported by the API, such as for filtering content or setting user preferences. The response likely includes language codes and possibly their corresponding names or additional metadata. Note that this endpoint doesn't accept any parameters, offering a static list of supported languages.

## Auth

Auth schemes: `API_KEY`.

## How agents use Listen Notes

Inside a Definable workflow, Listen Notes is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Listen Notes** — the Researcher (GPT-5.5) pulls context from Listen Notes (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Listen Notes** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Listen Notes (create record, post message, draft email).
- **Designer / Engineer → Distributor → Listen Notes** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Listen Notes (attach file, open PR comment, post status).

The Verifier checks every Listen Notes call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- video & audio — https://definable.ai/apps/category/video-&-audio/

## Related

- HTML page: https://definable.ai/apps/listennotes/
- Same category (video & audio): https://definable.ai/apps/category/video-&-audio/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt