403 Forbidden
The key was rejected, robots.txt disallowed the URL, or it resolves to a non-public address.
What causes it
- Invalid API key, the key was sent but did not match.
- Disallowed by robots.txt, the target site forbids crawling that path. This cannot be overridden through the API.
- Address not allowed, the URL resolves to a private, loopback, link-local, or carrier-grade NAT address, including through a redirect.
How to fix it
- Read the `title` field: the three causes are named distinctly.
- For a rejected key, check for a trailing newline or wrapping quotes from a copy-paste.
- For robots.txt, use the CLI with `--no-robots` on content you own.
- For a blocked address, this is working as intended, the API refuses to fetch anything that is not public internet.
What it looks like
{
"type": "https://snakereach.com/errors/address-not-allowed",
"title": "Address not allowed",
"status": 403,
"detail": "fetch failed for 169.254.169.254: blocked by address policy",
"url": "169.254.169.254"
}