Nothing was found at this path
HTTP status 404
This organization has nothing at this path. Domain names and ids are looked up in the token's own organization only.
From Pro up
The API knows the path, but the domain name or id in it leads to nothing the token can read. Usually the name is misspelled, or the token belongs to a different organization from the one you mean.
Why you get it
- The domain name is misspelled, or the domain has been archived or removed.
- The domain, report, source or export belongs to another organization. Another organization's data answers the same as data that does not exist, so this code never confirms that something is there.
- An id is not one the API gave out. Ids are numbers to copy, not to build.
- A report's file or an export's file is no longer stored, or the export failed. The
detailfield says which.
A path the API does not have at all, such as a misspelled endpoint or one ending in a slash, answers with an HTML error page instead of this problem. API paths have no trailing slash.
What to do
- Ask
GET /api/v1/organizationwhich organization the token belongs to. A token reads only the organization it was created in. - List the domains with
GET /api/v1/domainsand copy the name from the answer. - Take ids from the answers that list them, and send them back unchanged.
- For a failed or deleted export, start a new one.
Published 27 October 2026 · Checked 27 October 2026