Intelligence API error reference · Updated August 2026
parameter_unknown.
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.
A query parameter was supplied that this endpoint does not recognize. The request is rejected to prevent silent typos. Remove the unrecognized parameter or check the API reference for the canonical name.
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 400, the x-request-id header mirrors error.request_id, and the doc_url points back to this page.
{
"error": {
"type": "invalid_request_error",
"code": "parameter_unknown",
"message": "A query parameter was supplied that this endpoint does not recognize.",
"doc_url": "https://www.orbytlabs.ai/intelligence/api/errors/parameter_unknown",
"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 invalid_request_error family.