Hacker News Reader

Like the parameter passthrough feature. Take a look at places where the parameters are part of the URL structure. For example a Target product page http://www.target.com/p/men-s-c9-by-champion-impact-athletic...

In order to get data for a different product, I will have to modify the URL itself. I think same holds true for blog posts.

View on HN

Yes, it's a great point. We're working on updating the query param passthrough to handle params within the URL structure.

Apart from that here are other items. You may have these on your list, but can count my vote to prioritize.

1. Pagination 2. Image URLs 3. Focus on page types such as product pages, posts etc. That way its easy to go from content to content. Will help crawling too 4. Link back to original page included in JSON

Finally common sites/pages used by multiple users of your systems should not count against the API count requirement under pricing. You may want to charge against total calls, like Parse.

Thanks for the suggestions!

Reply on news.ycombinator.com