Scheduling API

Getting started

Before you start using this API, we recommend looking at the docs for our other APIs so you are aware of how to use them, since you will indirectly use them when creating schedules.

Callback functionality is mandatory for both Review Scraper API and Review Index API when using Scheduling API.

Schedules can be disabled or re-enabled as needed, and their name can be changed, but the rest of their metadata can’t be modified. Please refer to this section for more info.

Schedules will be automatically disabled if they fail to run 10 times in a row or if you don't have credits. You can re-enable them by updating the schedule.

We'll keep track of request IDs in case you need it. You can find the request ID in the response for GET /schedules/:schedule_id.

Scheduling API does not consume any credits by itself, only jobs that are created by the schedules do.

Any questions?

If you have further questions, do not hesitate to contact us at support@datashake.com.

Authorization

You must authorize your request using the x-api-key header.

You can use the token you received after subscribing to any of Datashake's APIs.

Diff crawling

For Review Scraper API, Scheduling API supports diff crawling. This means that the schedules you create will automatically only crawl new reviews that were not crawled before, saving you both time and credits.

Failed requests are taken into account, so do not worry about losing data. Diff crawling will scrape reviews starting from the last successful run.

Backlogged requests are also handled. If a request for a given schedule is still pending, the next run will be skipped to avoid sending duplicate data back to you.

Maximum number of schedules

You can create up to 500 schedules in total.

Once you go over your rate limit you will receive a 400 Bad Request error.

Do you need more?

If you need to increase the limit, please feel free to reach out.