The best podcast search engine.
Tools
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.
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.
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.
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.
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.
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.