Thanks for looking into it.

• Please can we make the code not depending on manually-entered <DATASET_ID> ? Basically so that you can run it and and see results right away
• I'd consider using an Actor that is not PPR, e.g. Website Content Crawler

Please can we make the code not depending on manually-entered <DATASET_ID> ? Basically so that you can run it and and see results right away

Sure, we can do that, but I would consider the learning and communication value of the code example on the Docs API landing page. I thought about having the API key exported at the very top and the dataset ID extracted with jq into another constant, but it seemed harder to read compared to having the reader manually replace the placeholders and understand what they’re doing.

If we want a super simple one-liner curl example to demo Apify (API), I'd consider adding a convenience API endpoint that:

• calls the actor
• waits for its start
• it streams the default dataset content.

(if that's even possible)

Yeah, cool, we have an API endpoint for that

@jancurn What about now? :) The Actor is "pay per usage" if I'm not mistaken, so it should work out of the box.

@netmilk looks good cheers