invalid_parameter: Invalid parameter

Havoptic API error invalid_parameter (HTTP 400, Invalid parameter): A query parameter, path parameter or request body field has a value the API does not accept. What it means and how to fix it.

What it means

The request was understood, but one of its inputs is out of range, malformed or not in the allowed set. The param field names the input; detail says what was expected.

Some 400 responses use the title "Invalid request" (for example an unparseable date). They share this type.

MCP tool calls report the same problem as a tool result with isError: true instead of an HTTP status.

Common causes

• An enum value the API does not know, e.g. kind=breakage instead of kind=breaking, or type=patch on /releases.
• An unknown tool id. Valid ids come from GET /v1/tools.
• A version range that cannot be resolved on /tools/{id}/upgrade (from is not a tracked version).
• A webhook body with a non-https url, a private or loopback host, an unknown event, or an unknown tool or change kind in filters.

How to fix it

• Read param and detail, correct that one input, and retry. Retrying the same request unchanged will fail again.
• Fetch allowed values instead of hard-coding them: tool ids from GET /v1/tools, change kinds from Typed changes, schemas from GET /v1/schemas/{name}.json.

Example response

{
  "type": "https://www.havoptic.com/docs/errors/invalid_parameter",
  "title": "Invalid parameter",
  "status": 400,
  "detail": "kind must be one of: feature, fix, breaking, …",
  "param": "kind"
}

All errors

Developer docs · API reference · OpenAPI · Havoptic