route_not_found
The path does not match any v1 endpoint. It is usually a typo, a missing `/v1` prefix, a path from a different area of the API, or the flat form of a route that the breaking window moved under the company or account segment; in that last case `error.subcode` is `legacy_route_moved`.
| Code | Type | HTTP | Category |
|---|---|---|---|
route_not_found | not_found_error | 404 | Request |
Cause
The path does not match any v1 endpoint. It is usually a typo, a missing /v1 prefix, a path from a different area of the API, or the flat form of a route that the breaking window moved under the company or account segment; in that last case error.subcode is legacy_route_moved.
What to do
With legacy_route_moved, repeat the call using error.details.replacement (method and path, with {company} or {account} still to fill in) and follow the guide at error.details.migration_guide_url. Otherwise, check the path in the API reference, base URL included (https://api.factuarea.com/v1).
Message returned by the API
Resource not found.