Challenges of Offering an API
Briefly

I need to make it hard to iterate over my database entries easily. If you're downloading record #4287, you know that there probably is a #4288 as well. That way, a scraper could be automated to grab every single record in a row. That's why I created encoded IDs in my API, just like Stripe, that both obfuscate the underlying ID and make the record more recognizable.
Any API I offer needs to be severely rate-limited. Podcast information, particularly historical data, doesn't change after the fact. Even with mild scraping, someone could eventually explore the whole API within a few months. That's where rate limits come on. My trial plan allows a measely 100 requests per day.
Read at The Bootstrapped Founder
[
add
]
[
|
|
]