I don't think there is anything in ToS
I don't think there is anything in ToS to prohibit this.
btw, how would you handle user killing a run?
2 Replies
At first, my plan was to process the charge from the run and then send the results from my server. This way, if a user aborted after being billed but before the results were delivered, a webhook would notify my API. My server could then check the run endpoint to verify the charges against the number of results/pages sent, and if there was a mismatch, it would upload the missing data to keep everything consistent. However, I’ve decided it’s simpler to just send the data directly from the run instead.
on the Apify API side, the charge for data happens inside the dataset.save() call. A user aborting after being charged but before data is saved, would be a very rare event. If it all possible (I imagine its not difficult for them to add a check and flush inside the abort call if needed)