Update Custom Metric

Update a specific custom metric by ID.

PUT /v1/update-custom-metric/{metric_id}

Update Custom Metric

cURL

curl --request PUT \
  --url https://api.getbluejay.ai/v1/update-custom-metric/{metric_id} \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <x-api-key>' \
  --data '
{
  "name": "<string>",
  "description": "<string>",
  "response_type": "pass_fail",
  "agent_ids": [
    123
  ],
  "min_value": 123,
  "max_value": 123,
  "category": "<string>",
  "tags": [
    "<string>"
  ],
  "scoring_guidance": "<string>",
  "eval_route": "AUTO",
  "model": "<string>",
  "audio_model": "<string>",
  "temperature": 123,
  "enum_options": [
    "<string>"
  ],
  "allow_not_applicable": true
}
'

200

{
  "id": "<string>",
  "name": "<string>",
  "description": "<string>",
  "response_type": "pass_fail",
  "created_at": "2023-11-07T05:31:56Z",
  "agent_ids": [
    123
  ],
  "min_value": 123,
  "max_value": 123,
  "category": "<string>",
  "tags": [
    "<string>"
  ],
  "scoring_guidance": "<string>",
  "eval_route": "AUDIO",
  "model": "<string>",
  "audio_model": "<string>",
  "temperature": 123,
  "enum_options": [
    "<string>"
  ],
  "allow_not_applicable": false
}

Integration Prompt for AI Agents

# Bluejay — Testing & Monitoring Platform for Conversational AI Agents

You are a senior backend engineer integrating the Bluejay API. Think step-by-step: first understand the endpoint, then plan the integration, then implement with minimal changes.

## Update Custom Metric — PUT /v1/update-custom-metric/{metric_id}

> **What this endpoint does:** Update a specific custom metric by ID.

**Endpoint:** PUT `https://api.getbluejay.ai/v1/update-custom-metric/{metric_id}`
**Auth:** `X-API-Key` header
**Content-Type:** application/json

### Required Parameters
| Name | Type | Description |
|------|------|-------------|
| metric_id | string |  |
| X-API-Key | string | API key required to authenticate requests. |

Review the full parameter list at https://docs.getbluejay.ai/api-reference/endpoint/update-custom-metric and include any optional parameters (e.g., `name`, `description`, `response_type`, `agent_ids`, `min_value`, `max_value`) that serve your integration's use case and align with Bluejay's testing and monitoring capabilities.

### Request Body
```json
{
  "name": "string",
  "description": "string",
  "response_type": "pass_fail",
  "agent_ids": [
    123
  ],
  "min_value": 1.0,
  "max_value": 1.0,
  "category": "string",
  "tags": [
    "string"
  ],
  "scoring_guidance": "string",
  "eval_route": "AUDIO",
  "model": "string",
  "temperature": 1.0,
  "enum_options": [
    "string"
  ],
  "allow_not_applicable": true
}
```

### Example
**PUT with body:**
```python
import requests

def update_custom_metric(metric_id: str, payload: dict, api_key: str) -> dict:
    url = f"https://api.getbluejay.ai/v1/update-custom-metric/{metric_id}"
    headers = {"X-API-Key": api_key}
    response = requests.put(url, headers=headers, json=payload)
    response.raise_for_status()
    return response.json()
```

### Constraints
- Minimal changes — only add/change files needed for this integration.
- Match existing codebase patterns (naming, file structure, error handling).
- Include error handling for 422: Validation Error.

### Integration Checklist
Before writing code, verify:
1. Which module/service owns this API domain in the codebase?
2. What HTTP client and error-handling patterns does the project use?
3. Are there existing types/interfaces to extend?

Then implement the integration, export it, and confirm it compiles/passes lint.

This endpoint allows you to update an existing custom metric for your agents. Provide the metric ID and updated details to update the metric.

Headers

X-API-Key · string · required

API key required to authenticate requests.

Path Parameters

metric_id · string<uuid> · required

Body

application/json

Request model for updating a custom metric

name · string | null

Name of the custom metric

description · string | null

Description of what this metric measures

response_type · enum<string> | null

Type of response expected

Available options: pass_fail, yes_no, qualitative, quantitative, json, enum

agent_ids · integer[] | null

List of agent IDs to associate this metric with (replaces existing associations)

min_value · number | null

Minimum value for quantitative metrics

max_value · number | null

Maximum value for quantitative metrics

category · string | null

Category for organizing metrics

tags · string[] | null

Tags for categorizing the metric

scoring_guidance · string | null

Guidance on how to score this metric

eval_route · enum<string> | null · default: AUTO

Route for evaluating the metric

Available options: AUDIO, TEXT, AUTO

model · string | null

Model to use for text evaluation of the metric

audio_model · string | null

Model to use for audio evaluation of the metric

temperature · number | null

Temperature for evaluating the metric

enum_options · string[] | null

Options for enum metrics

allow_not_applicable · boolean | null

Whether this metric allows 'not applicable' responses.

Response

200

application/json

Successful Response

Response model for custom metric operations

id · string · required

Unique identifier for the custom metric

name · string · required

Name of the custom metric

description · string · required

Description of what this metric measures

response_type · enum<string> · required

Type of response expected

Available options: pass_fail, yes_no, qualitative, quantitative, json, enum

created_at · string<date-time> · required

When this metric was created

agent_ids · integer[]

List of agent IDs this metric belongs to

min_value · number | null

Minimum value for quantitative metrics

max_value · number | null

Maximum value for quantitative metrics

category · string | null

Category for organizing metrics

tags · string[] | null

Tags for categorizing the metric

scoring_guidance · string | null

Guidance on how to score this metric

eval_route · enum<string> | null

Route for evaluating the metric

Available options: AUDIO, TEXT, AUTO

model · string | null

Model to use for text evaluation of the metric

audio_model · string | null

Model to use for audio evaluation of the metric

temperature · number | null

Temperature for evaluating the metric

enum_options · string[] | null

Options for enum metrics

allow_not_applicable · boolean · default: false

Whether this metric allows 'not applicable' responses.