Telnyx · Schema

TestRunResponse

Response model containing test run execution details and results. Provides comprehensive information about a test execution including status, timing, logs, and detailed evaluation results.

CommunicationsCPaaSVoiceSMSIoTTelecommunicationsMessagingArtificial IntelligenceMCPVoice AIPhone NumbersInference

Properties

Name Type Description
completed_at string Timestamp when the test run finished execution.
conversation_id string Identifier of the conversation created during test execution.
conversation_insights_id string Identifier for conversation analysis and insights data.
created_at string Timestamp when the test run was created and queued.
detail_status array Detailed evaluation results for each rubric criteria. Name is name of the criteria from the rubric and status is the result of the evaluation. This list will have a result for every criteria in the ru
logs string Detailed execution logs and debug information.
run_id string Unique identifier for this specific test run execution.
status object
test_id string Identifier of the assistant test that was executed.
test_suite_run_id string Identifier linking this run to a test suite execution batch.
triggered_by string How this test run was initiated (manual, scheduled, or API).
updated_at string Timestamp of the last update to this test run.
View JSON Schema on GitHub

JSON Schema

telnyx-test-run-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/telnyx/main/json-schema/telnyx-test-run-response-schema.json",
  "title": "TestRunResponse",
  "description": "Response model containing test run execution details and results.\n\nProvides comprehensive information about a test execution including\nstatus, timing, logs, and detailed evaluation results.",
  "x-generated": "2026-10-08",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/telnyx-assistants-api-openapi.yml#/components/schemas/TestRunResponse",
  "properties": {
    "completed_at": {
      "description": "Timestamp when the test run finished execution.",
      "format": "date-time",
      "title": "Completed At",
      "type": "string"
    },
    "conversation_id": {
      "description": "Identifier of the conversation created during test execution.",
      "title": "Conversation Id",
      "type": "string"
    },
    "conversation_insights_id": {
      "description": "Identifier for conversation analysis and insights data.",
      "title": "Conversation Insights Id",
      "type": "string"
    },
    "created_at": {
      "description": "Timestamp when the test run was created and queued.",
      "format": "date-time",
      "title": "Created At",
      "type": "string"
    },
    "detail_status": {
      "description": "Detailed evaluation results for each rubric criteria. Name is name of the criteria from the rubric and status is the result of the evaluation. This list will have a result for every criteria in the rubric section.",
      "items": {
        "$ref": "#/$defs/TestRunDetailResult"
      },
      "title": "Detail Status",
      "type": "array"
    },
    "logs": {
      "description": "Detailed execution logs and debug information.",
      "title": "Logs",
      "type": "string"
    },
    "run_id": {
      "description": "Unique identifier for this specific test run execution.",
      "format": "uuid",
      "title": "Run Id",
      "type": "string"
    },
    "status": {
      "$ref": "#/$defs/TestStatus"
    },
    "test_id": {
      "description": "Identifier of the assistant test that was executed.",
      "format": "uuid",
      "title": "Test Id",
      "type": "string"
    },
    "test_suite_run_id": {
      "description": "Identifier linking this run to a test suite execution batch.",
      "format": "uuid",
      "title": "Test Suite Run Id",
      "type": "string"
    },
    "triggered_by": {
      "description": "How this test run was initiated (manual, scheduled, or API).",
      "title": "Triggered By",
      "type": "string"
    },
    "updated_at": {
      "description": "Timestamp of the last update to this test run.",
      "format": "date-time",
      "title": "Updated At",
      "type": "string"
    }
  },
  "required": [
    "run_id",
    "test_id",
    "status",
    "triggered_by",
    "created_at"
  ],
  "type": "object",
  "$defs": {
    "TestRunDetailResult": {
      "properties": {
        "name": {
          "title": "Name",
          "type": "string"
        },
        "status": {
          "$ref": "#/$defs/TestStatus"
        }
      },
      "required": [
        "name",
        "status"
      ],
      "title": "TestRunDetailResult",
      "type": "object"
    },
    "TestStatus": {
      "description": "Represents the lifecycle of a test:\n  - 'pending': Test is waiting to be executed.\n  - 'starting': Test execution is initializing.\n  - 'running': Test is currently executing.\n  - 'passed': Test completed successfully.\n  - 'failed': Test executed but did not pass.\n  - 'error': An error occurred during test execution.",
      "enum": [
        "pending",
        "starting",
        "running",
        "passed",
        "failed",
        "error"
      ],
      "title": "TestStatus",
      "type": "string"
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/telnyx-test-run-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.