apify_run_actor hands back a run id and the id of the dataset the results will land in, apify_get_run says when it is done, and apify_get_dataset_items returns the rows. Because the server is hosted, your Apify token is linked once in the provider's dashboard instead of sitting in a local config file.
A hosted server over the Apify API. It lists the Actors in your account, starts one with input you supply, reports on the run, and returns the rows the run scraped.
- The Actors in your account, paged, each with its id, name and owner
- An Actor started with JSON input, plus optional run timeout, memory ceiling and build tag
- A run's status and metadata, with the option to wait for it to finish rather than poll
- Recent runs listed newest first, filterable to just the failed or just the running ones
- Scraped rows read out of a run's dataset, paged, with Apify's internal fields stripped by default
- Saved Actor tasks listed, so pre-configured jobs show up next to ad-hoc runs
- A health check that says whether the server is reachable at all
An Apify API token, created in the Apify console. A personal token carries your whole account's permissions, so create a scoped one for anything that runs unattended. This is a hosted server rather than one you run locally: you link the Apify token in the provider's dashboard, requests carry your bearer token plus the identifier of that linked credential, and calls draw down the provider's own credit balance.