1. Why do I have to use Listen API?
You always have other options:
You can either build and maintain your own podcast database, or choose other podcast apis on the Internet.
We make it very easy for you to try out Listen API. We don't ask you to talk to any sales people,
and we don't require you to "request a demo".
subscribe to FREE plan without entering credit card info and start using Listen API in seconds
Whenever you have any questions, you can get quick answers from [email protected]
-- you'll directly talk to
the founder & CEO of Listen Notes
2. How hard it could be to build a podcast database?
Building a decent podcast database is an ongoing effort.
It's not hard. But it takes time and money (e.g., server bills, engineer salaries...) to build and maintain.
Just like owning a car or a house, the initial expense to buy is way less than the ongoing cost to maintain (
e.g., tax, insurance, unexpected costs...).
You may want to read
this blog post to learn the technology behind Listen Notes
, if you decide to replicate what we do here at Listen Notes.
Actually, the most expensive part of building your own podcast database is the opportunity cost
It's about making choice. The time spent building your own podcast database is the time you can't use to build your apps (or websites).
Using Listen API allows you to jumpstart the most exciting part of your project immediately.
3. Are you actively supporting the API? Do you expect to continue to do so?
Yes. Listen API powers our user-facing website ListenNotes.com. Listen API benefits from most backend improvements of ListenNotes.com.
We've been around since 2017 and we plan on being around for a long time.
4. If we use Listen API and it goes away in the future…
Your concern is valid. We all know that NOT ANY online services or companies can last forever.
If we decide to shut down Listen API, we’ll give you (at least) 12 weeks’ notice and you’ll be able to buy the latest database dump (all podcasts + all episodes) at a reasonably low price.
It's very likely that Listen Notes will outlive many well-funded startups or even public companies.
We run Listen Notes lean. Unlike other bigger companies, we don't employ tons of people,
so we don't need to pay tons of salaries and it's unlikely that our company will shut down due to internal power struggle.
We are able to architect the software infrastructure to be robust enough while not wasting tons of money on server bills.
5. Do you provide any support?
Yes. If you have any questions about Listen API, just email [email protected]
Unlike talking to an average customer service guy in other lame companies,
you talk to the founder and CEO of Listen Notes, Inc.
directly, who built this whole thing by hand & by heart.
6. If my app becomes so successful, will you copy my idea?
No. We are not interested in building apps.
For us at Listen Notes, the minute spent building apps is the minute that we can't improve the podcast search engine,
the podcast database, the podcast api...
In addition, ideas are cheap and execution is everything. If it's so easy to copy a startup idea, then big companies always win.
Good luck for your business.
7. We'll use tons of API requests. Are you able to support our scale?
Right now, there are developers doing millions of requests/month with Listen API.
We can easily support at least 10x of current traffic without adding more servers.
8. Can we cache the API response on the client side (e.g., inside the app or the web browser...)?
but you can't cache on the server side, except for podcast/episode ids and pub_dates.
In other words, you can permanently store only podcast/episode ids and pub_dates on the server side, e.g., in your own database.
9. In the API response, why audio urls and RSS urls are from the listennotes.com domain name?
To be clear, we don't store audios or RSS feeds on our own servers.
Podcasters will get accurate analytics data, e.g., the listener's ip, user-agent...
We wrap the actual urls with our own urls (HTTP 301
because podcasts often change audio urls and RSS urls, and we want
to help you and your users figure out the correct urls.
It's a common practice for apps to cache data on the client side for performance optimization.
Apps cache the permanent Listen Notes urls on the client side,
while we figure out the correct audio urls and RSS urls from the server side -- we constantly check if podcasts change audio / RSS urls from our end.
10. What if we can't find a particular podcast? What if the data is not in sync with the RSS feed (e.g., audios are broken, incorrect podcast meta data...)?
Although our podcast database is very comprehensive, it's possible that we don't add some new shows in time.
In this case, you can help submit the missing shows
It's also possible that the podcast creator changes the RSS feed and we don't catch the changes in time.
In this case, you can report to us via [email protected]
If you subscribe to the PRO plan and use over 1 million API requests per month,
we can give you a tool to refresh the RSS feed of podcasts on your end.
11. How do you make sure your podcast database is up-to-date?
To find new podcasts, we use three approaches.
First, we run crawlers 24/7 to find publicly accessible podcasts on the Internet, which is similar to how Google or other search engines find new websites.
Second, podcasters submit new shows
to Listen Notes on their own -- we get dozens of new submissions from podcasters everyday.
Third, if we see any missing podcasts, we manually add them to our database.
We check the RSS feed of all podcasts 24/7.
For recently listened podcasts (based on our website and API traffics), new episodes would be added to our database within 1 hour (typically within 15 to 30 minutes).
For other podcasts, new episodes would be fetched within a few hours (typically 2 to 4 hours).
The two most common cases that an API user gets suspended:
1. Create multiple accounts to get around the quota limit of FREE plan, especially using disposable email addresses
2. Cache most of the response data on the server side.