chore: copy & paste friendly curl API example

[netmilk]

• the commands are restructured in a way that the editable part is always at the end of the snippet (especially annoying in multi-line snippets)
• added the saving of the response of the Run to a run.json
• added convenience jq command to find the dataset in the Actor run response
• removed (imo) unnecessary quotes
• squished the per command line breaks to save lines

Please, try it yourself before merging:

# Prepare Actor input
echo '{ "searchStringsArray": ["Apify"] }' > input.json

# Run the Actor and retreive its default dataset id.
curl -X POST -d @input.json -H 'Content-Type: application/json' \
  -s -o >(tee run.json) \
  https://api.apify.com/v2/acts/compass~crawler-google-places/runs?token=<YOUR_API_TOKEN>

# Find the defaultDatasetId in the API response 
cat run.json | jq -r .data.defaultDatasetId

# And pass it instead of <DATASET_ID>
curl https://api.apify.com/v2/datasets/<DATASET>/items?token=<YOUR_API_TOKEN>

[jancurn]

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

[netmilk]

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)

[jancurn]

Yeah, cool, we have an API endpoint for that