invalid_url
invalid_url
Section titled “invalid_url”HTTP status: 400 Bad Request
How to fix
Section titled “How to fix”- Prepend the scheme.
example.com/page→https://example.com/page. We do not auto-prepend because guessing wrong silently is worse than failing loudly. - URL-encode special characters. Spaces become
%20,#becomes%23, etc. Most HTTP clients do this for you; raw shell command-lines often don't. - Strip stray whitespace. A leading or trailing space breaks parsing.
trim()the value before submitting. - Reject private and link-local hosts.
localhost,127.0.0.1,192.168.*,10.*,169.254.*are blocked by our SSRF guard and return this same code.
What this means
Section titled “What this means”The URL string failed validation before we ever dispatched a scrape job. Either the format is wrong (no scheme, bad characters) or the target host is on our blocklist for SSRF reasons. The param field in the error body tells you which field failed — usually url, sometimes urls[3] for batch submits.
Related errors
Section titled “Related errors”invalid_input— generic field-level validation failure for non-URL fieldsinvalid_workflow— the workflow JSON itself is malformed
Still stuck?
Section titled “Still stuck?”Contact support with your request_id (looks like req_01HF3JKB...). Include the exact URL you submitted so we can reproduce.