GoCD API

Name: GoCD API
Brand: GoCD API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi Cdbearer, basic44 EndpointsREST

For Agents

Trigger GoCD pipelines, manage build agents and environments, and rotate access tokens. Built for DevOps agents that drive continuous delivery on self-hosted GoCD servers.

Connect the GoCD API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GoCD API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with GoCD API.

Create or update pipeline definitions and inspect their configuration

Read pipeline run history to see which builds passed or failed

Manage build agents and assign them to environments

Configure pipeline groups and security roles for fine-grained access control

GET STARTED

Start building with GoCD API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for GoCD API, keeping it validated and agent-ready. The GoCD API is the REST surface for ThoughtWorks' open-source continuous-delivery server. It exposes pipelines, pipeline groups, agents, environments, users, security roles, materials, configuration repositories, access tokens, system backups, and health checks. It is the standard interface for triggering deployments, managing build agents, and rotating access credentials in self-hosted GoCD installations.

Use Cases

Patterns agents use GoCD API for, with concrete tasks.

★ Pipeline Triggering and Monitoring

DevOps teams call GET /admin/pipelines to inspect a pipeline definition and GET /pipelines/{pipeline_name}/history to read recent runs. The pipeline detail and history endpoints together let an agent decide whether to trigger a redeploy after a failed run or roll back to the previous successful build.

Pull the last 5 runs of pipeline 'release-backend' and trigger a new run if the most recent run failed.

Build Agent Fleet Management

Operations teams use the /agents endpoints to register, retire, or assign build agents to specific environments via /admin/environments. This keeps build capacity aligned with workload, particularly when scaling agents up or down on demand.

List all GoCD agents tagged 'gpu-builds', remove any that have been offline for more than 24 hours, and report the result to Slack.

Access Token and Backup Hygiene

Security and platform teams rotate personal access tokens via /access_tokens and trigger configuration backups through /admin/backup. The backup endpoint returns a job that captures the GoCD configuration so it can be restored after a server failure or migration.

Revoke every GoCD access token older than 90 days and trigger a configuration backup.

AI Agent CI/CD Operations

An AI agent uses Jentic to drive deployments end-to-end: it lists pipelines, checks history, triggers a build, and posts the outcome to a chat channel. Bearer credentials stay in the Jentic vault and the agent only ever sees schema-level metadata.

Search Jentic for 'trigger gocd pipeline', load the schema, and trigger pipeline 'release-frontend' with the latest material revision.

Key Endpoints

44 endpoints — jentic publishes the only available openapi specification for gocd api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/admin/pipelines

List pipeline definitions

GET

/admin/pipelines/{pipeline_name}

Read a pipeline definition

GET

/pipelines/{pipeline_name}/history

Get pipeline run history

GET

/agents

List build agents

GET

/admin/environments

List environments

POST

/access_tokens

Create a personal access token

POST

/admin/backup

Trigger a configuration backup

GET

/health

Check server health

GET

/admin/pipelines

List pipeline definitions

GET

/admin/pipelines/{pipeline_name}

Read a pipeline definition

GET

/pipelines/{pipeline_name}/history

Get pipeline run history

GET

/agents

List build agents

GET

/admin/environments

List environments

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

GoCD bearer tokens and basic-auth credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g. 'trigger gocd pipeline') and Jentic returns matching GoCD operations with their input schemas, so the agent can call the right endpoint across 44 paths without browsing docs.

Time to first call

Direct GoCD integration: 1-3 days for token handling and pipeline JSON shaping. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using GoCD API through Jentic.

Why is there no official OpenAPI spec for GoCD API?

GoCD documents its REST endpoints in HTML reference pages but does not publish a maintained OpenAPI specification. Jentic generates and maintains this spec so AI agents and developers can call GoCD API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the GoCD API use?

GoCD supports two schemes: HTTP bearer tokens (personal access tokens) and HTTP basic authentication for local users. Through Jentic, both are stored encrypted in the vault and injected at execution time so the agent never sees the raw secret.

Can I list pipeline run history with the GoCD API?

Yes. GET /pipelines/{pipeline_name}/history returns the recent run history for a named pipeline, including status and material revisions, so an agent can detect failures and decide on retries.

What are the rate limits for the GoCD API?

GoCD is self-hosted and the OpenAPI spec does not declare a numeric rate limit. The practical limit depends on the deployed server's capacity; back off on HTTP 429 responses if your administrator has fronted the server with a rate-limiting proxy.

How do I trigger a GoCD pipeline through Jentic?

Run a Jentic search for 'trigger gocd pipeline', load the schema for the relevant /admin/pipelines or scheduling endpoint, and execute it with the pipeline name. Install with pip install jentic and chain search, load, and execute.

Does the GoCD API support config backups?

Yes. POST /admin/backup triggers a configuration backup. The endpoint returns a job that captures the GoCD configuration so it can be restored after a server failure or migration.