Harness Ci

Harness provides a REST API under /api/pipelines/, /api/executions/, /api/triggers/. Key operations: POST /api/pipelines/{pipelineId}/trigger (trigger execution with input set), GET /api/executions/{executionId} (poll status), GET /api/pipelines (list pipelines), GET /api/executions (list executions with filters). Authentication uses x-api-key header with Personal Access Tokens or Service Account Tokens. The API follows REST conventions with JSON. Pagination uses pageIndex/pageSize parameters. Rate limits are not prominently documented.

Harness API returns standard HTTP status codes with JSON response envelopes. Pipeline trigger responses include an execution ID for polling. Execution status responses include status (RUNNING, SUCCESS, FAILED, ABORTED), stage breakdown, and failure details when applicable. Failed pipeline responses include AI-generated failure summaries when test intelligence is enabled. Rate limit responses include retry headers. Error messages are descriptive. Webhook triggers include signature verification for security.

Harness CI is a cloud-native continuous integration platform with AI-assisted test intelligence and failure analysis. It provides a REST API for managing pipelines, triggering builds, querying execution status, and managing artifacts — making it agent-accessible for CI/CD automation workflows. Agents can trigger pipelines on demand, poll for completion, retrieve test results, and parse failure summaries. Harness uses YAML pipeline definitions with support for Kubernetes, Docker, and cloud build environments. Free tier is available (Harness Cloud). On-premise deployment is supported. Confidence is docs-derived; test intelligence quality is not runtime-verified.

Authentication uses API keys (x-api-key header). Personal Access Tokens are scoped per user; Service Account Tokens are scoped to accounts/orgs/projects and are the recommended pattern for agent use. Keys are created and managed in the Harness platform UI. Token scopes align with Harness's account/organization/project hierarchy — appropriate scoping reduces blast radius. No per-pipeline key scoping documented.

Documentation at developer.harness.io covers pipeline setup, API reference, YAML reference, and integration guides. The REST API reference is comprehensive. Getting started guides cover multiple CI environments (Kubernetes, VM, cloud build). Community support via Slack and GitHub. Documentation quality is good for the core CI use case; some API endpoints have limited example coverage. Harness's AI features are documented but their reliability is marketing-adjacent in claims.