NO_RESULTS

Defined for an empty discovery result, but /v1/map always returns at least the start URL.

NO_RESULTS is meant for a discovery call that finds nothing. In practice you won't see it. When a site has no usable sitemap and no links, /v1/map falls back to the start URL itself, so the list is never empty. The same is true for /v1/batch with `site`.

HTTP 404. Body always includes code: "NO_RESULTS". Branch on code, never on the human-readable message — wording can change without notice; the code is the stable contract.

{
  "status": "error",
  "code": "NO_RESULTS",
  "message": "No URLs discovered for https://example.com."
}

You can handle it as an empty list, but don't expect it. If /v1/map returns only the start URL, Onto found no usable sitemap and no same-host links on that page. Read the URLs you already know with /v1/read instead.

Suggested handling in a Node client:

if (data.code === 'NO_RESULTS') {
  // Valid call, empty result — fall back to known URLs.
  return [];
}

See the full error index for the complete catalog with the handling switch statement covering every code at once.