Intelligence API error reference · Updated August 2026
data_point_not_found.
HTTP 404not_found_errorDo not retry
Every Orbyt Intelligence error envelope carries a permanent doc_url that resolves here. This page is generated from the same error registry the API serves from, so it can never drift from runtime behavior.
What it means.
The lineage lookup target does not exist. The data point may have been retracted or never published; check the corrections feed.
Retry strategy.
The envelope returns retry_strategy: "do_not_retry" by default for this code.
Retrying the same request will fail again. Fix the underlying cause first, then issue a fresh request.
Example error envelope.
Locked RFC-001 shape. The HTTP status is 404, the x-request-id header mirrors error.request_id, and the doc_url points back to this page.
{
"error": {
"type": "not_found_error",
"code": "data_point_not_found",
"message": "The lineage lookup target does not exist.",
"doc_url": "https://www.orbytlabs.ai/intelligence/api/errors/data_point_not_found",
"request_id": "req_0123456789abcdef",
"retry_strategy": "do_not_retry"
}
}How to fix it.
- Read error.message for the specific cause. It is written to be quoted verbatim.
- Fix the cause in your integration (key, scope, tier, or request shape) before sending the request again.
- If you believe the error is wrong, contact support with the error.request_id so we can pull the exact log row.
Related codes.
Other codes in the not_found_error family.