Skip to main content
Set JSON output once for agent sessions:

Scraper Sequence

1

Confirm account and price

Inspect balance, priceEvents[].usdMicros, and usage.billingEstimate.lineItems before high-count Requests.
2

Inspect scraper availability

3

Create paid public-data work

4

Poll and read results

Use --cursor <nextCursor> with tovuk request list and tovuk request results to continue request and stored-result pagination. For ecommerce Records, inspect featureCoverage to see whether requested Apify-style fields were extracted, absent, partially extracted, or accepted for compatibility. Public metadata fields can include tags, keywords, questionSamples, customerPhotoUrls, minimumOrderQuantity, rfqText, resultPosition, and adPosition.
5

Cancel when needed

Public-Data Rule

Scraper Requests are for public data only. Do not send cookies, passwords, account tokens, private session data, private account content, private repository credentials, or proxy URLs.

Support

Open support tickets only after capturing the request id, exact command, and first actionable error:
AI/API agents can also call POST /v1/support/tickets directly with an account API key or session bearer token. Support tickets are account-scoped service tickets between the authenticated account and Tovuk for scraper, billing, API key, and account help. Ticket responses include created_by so later agents can see whether the ticket came from an account session or account API key.
Last modified on July 7, 2026