v1
latestOpenAPI 3.1.02026-07-22152755.8 KBRetrieve a metric
Fetch one metric by id.
Path parameters
ID or Slug - Metric identifier. Can be either:
- Numeric ID (e.g., 123)
- Slug (e.g., latency_metric, customer_satisfaction)
Response
URL-friendly unique identifier in snake_case format. Example: "customer_satisfaction_1562"
Name of the metric. Example: "Customer Satisfaction" or "Appointment Booking"
Description of what the metric measures. Example: "Measures how satisfied customers are with the service provided"
Type of metric
- basic - Basic (Deprecated in favor of LLM Judge)
- custom_prompt - Custom Prompt ( Deprecated in favor of LLM Judge)
- custom_code - Custom Code
- llm_judge - LLM Judge
- binary - Binary
- continuous_qualitative - Continuous Qualitative
- numeric - Numeric
- enum - Enum
Whether this metric requires audio analysis. Example: true or false
Evaluation prompt for the metric. Example: "Evaluate customer satisfaction based on conversation"
- always - Always
- automatic - Automatic
- custom - Custom
Type of trigger evaluation: LLM judge or custom code. Only used when evaluation_trigger is CUSTOM. Example: "llm_judge" or "custom_code"
- llm_judge - LLM Judge
- custom_code - Custom Code
Evaluation trigger prompt for the metric. Example: "Evaluate metric only if call ended reason is main-agent-ended-call"
Python custom code to determine metric relevance. Code should set _result (bool) and _explanation (str). Example: