One POST. Clean JSON back.

Every Datapika actor runs through the Apify REST API. The synchronous endpoint below returns dataset rows directly; runs longer than 300 seconds should switch to the async run-then-poll pattern. Get a token from your Apify account. Datapika publishes these tools as openclawai; Apify provides the API and billing. Result events, start fees and other applicable usage charges determine the total cost.

Quick start

curl -X POST \
  "https://api.apify.com/v2/acts/openclawai~job-board-scraper/run-sync-get-dataset-items?format=json" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "searchTerm": "data engineer",
    "location": "New York, NY",
    "sites": ["linkedin", "indeed", "glassdoor"],
    "maxResults": 20
  }'

OpenAPI specs, per actor

Each actor publishes a machine-readable OpenAPI spec for its default build, no auth required. Point your codegen or your agent at it.

Good to know

  • Check each actor’s pricing for result events, start fees, optional events and platform or plan charges. Set a supported run budget with maxTotalChargeUsd and review the estimate before execution; do not assume an empty run is free.
  • The sync endpoint returns 408 after 300 seconds; large sweeps should start a run, then poll and read the dataset.
  • Schedules and webhooks are built into the platform: run any actor every morning and push rows to your stack.