Skip to main content
Collect the exact request id, command, and first actionable error before creating a ticket.
tovuk support list --limit 20 --json
tovuk support create "Request failed" "Request failed after retry." --request-id request_123 --scraper-id tiktok --failing-command "tovuk request show request_123 --json" --first-log-line "upstream timeout" --severity normal --json
tovuk support resolve ticket_0123456789abcdef0123 --json
Support ticket creation is rate-limited per account. Resolve tickets after the issue is fixed so later automated runs do not duplicate work. Tickets are account-scoped service tickets between your account and Tovuk for scraper, billing, API key, and account help. Ticket responses include created_by so users and AI/API agents can see whether the ticket came from an account session or account API key.

API

GET /v1/support/tickets
POST /v1/support/tickets
POST /v1/support/tickets/{ticket_id}/resolve
Create body:
{
  "subject": "Request failed",
  "details": "Request failed after retry.",
  "request_id": "request_123",
  "scraper_id": "tiktok",
  "failing_command": "tovuk request show request_123 --json",
  "first_log_line": "upstream timeout",
  "severity": "normal"
}
AI/API agents can create the same ticket directly with an account API key or session bearer token:
curl -sS https://api.tovuk.com/v1/support/tickets \
  -H "Authorization: Bearer $TOVUK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "subject": "Request failed",
    "details": "Request failed after retry.",
    "request_id": "request_123",
    "scraper_id": "tiktok",
    "failing_command": "tovuk request show request_123 --json",
    "first_log_line": "upstream timeout",
    "severity": "normal"
  }'
Last modified on June 25, 2026