Skip to main content
GET
/
v1
/
custom-harnesses
/
{harness_id}
Get Custom Harness
curl --request GET \
  --url https://api.example.com/v1/custom-harnesses/{harness_id}
{
  "harness": {
    "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "team_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "name": "<string>",
    "agent_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "created_at": 123,
    "updated_at": 123,
    "created_by": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "description": "<string>",
    "persona_ids": [
      "3c90c3cc-0d44-4b50-8888-8dd25736052a"
    ],
    "policy_ids": [
      "3c90c3cc-0d44-4b50-8888-8dd25736052a"
    ],
    "status": "draft",
    "workflow_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "s3_key": "<string>",
    "generated_at": 123,
    "prompt_count": 123,
    "creation_error": "<string>"
  },
  "workflow": {
    "phase": "<string>",
    "error_message": "<string>",
    "task_id": "<string>",
    "session_id": "<string>"
  }
}

Path Parameters

​
harness_id
string<uuid>
required

Query Parameters

​
team_id
string<uuid> | null

Team ID (required)

Response

Successful Response

Response model for custom harness with optional workflow status.

​
harness
CustomHarness · object
required

Domain model for a custom harness (test configuration).

A custom harness is a test configuration that combines an agent, personas, and policies. The backend generates evaluation prompts based on this configuration.

Stored as metadata.json in S3.

​
workflow
WorkflowStatusInfo · object

Workflow status information for enrichment.

For custom harness workflows, task_id and session_id (when present) are persisted in the workflow S3 file under workflow_specific_fields and exposed here for cancel/debugging.

Last modified on April 21, 2026