Skip to content
Truto

Unified API

Unified CI/CD API

One standardized interface to read and write continuous integration & deployment data across every provider. 11 unified resources, 9 supported integrations, zero provider-specific code.

https://api.truto.one/unified/ci-cd
Start integrating API docs
11

Unified resources

9

Supported integrations

Pass‑through

Real-time, no data storage

Data Model

CI/CD resources

Every resource is normalized across providers. Use the same schema whether your customer is on Azure DevOps or Bitbucket.

Artifacts

The artifact represent an artifact in the CI/CD.

10 fields Docs →
Artifacts fields
id string
name string
workflow string
build string
size_in_bytes integer
download_url string
created_at string
updated_at string
expires_at string
expired boolean

Branch-protection-rules

The branch protection rule represents protection settings applied to branches in a repository

13 fields Docs →
Branch-protection-rules fields
id string
name string
repos array
pattern string
is_active boolean
require_owner_approval boolean
required_checks array
access_restrictions object
integration_restrictions object
allow_branch_deletion boolean
created_by object
created_at string
updated_at string

Branches

The branch represent a branch in the CI/CD.

9 fields Docs →
Branches fields
id string
name string
repo string
last_commit string
last_commit_by string
last_commit_message string
last_commit_at string
created_at string
updated_at string

Builds

The build represent a build in the CI/CD.

18 fields Docs →
Builds fields
id string
name string
repo string
branch string
commit string
trigger string
triggered_by string
triggered_by_type string
conclusion string
workflow string
build string
status string
created_at string
updated_at string
started_at string
completed_at string
attempts integer
number integer

Caches

The cache represent a cache in the CI/CD.

8 fields Docs →
Caches fields
id string
branch string
key string
version string
created_at string
updated_at string
last_used_at string
size_in_bytes integer

Jobs

The job represent a job in the CI/CD.

12 fields Docs →
Jobs fields
id string
name string
build string
status string
conclusion string
commit string
branch string
attempts integer
created_at string
updated_at string
started_at string
completed_at string

Organizations

The Organization object is used to represent an organization.

4 fields Docs →
Organizations fields
id string
name string
created_at string
updated_at string

Pull-requests

12 fields Docs →
Pull-requests fields
id string
title string
number integer
description object
status string
base_branch object
head_branch object
author object
closed_at string
merged_at string
created_at string
updated_at string

Repos

The repo represent a repository in the CI/CD.

11 fields Docs →
Repos fields
id string
name string
description string
owner string
owner_type string
visibility string
vcs_url string
status string
default_branch string
created_at string
updated_at string

Workflow

The workflow represent a CI/CD workflow.

2 fields Docs →
Workflow fields
id string
name string

Workspaces

The Workspace object is used to represent a workspace within a company.

4 fields Docs →
Workspaces fields
id string
name string
created_at string
updated_at string

Integrations

9 integrations, one API

Connect to any of these providers through the Unified CI/CD API. Same resources, same schema, same code.

Azure DevOps Bitbucket Buddy CircleCI Gerrit GitHub GitLab Jenkins Travis CI

How It Works

From zero to integrated

Go live with the Unified CI/CD API in under an hour. No boilerplate, no maintenance burden.

01

Connect your customer’s account

Use Truto’s pre-built auth flows to connect any continuous integration & deployment provider. OAuth, API keys, and custom auth — all handled.

02

Query the unified API

Read and write data through a single, normalized REST API. Same endpoints, same schema, regardless of the underlying provider.

03

Customize with JSONata

Need a field the unified model doesn’t cover? Extend the schema with declarative JSONata mappings — no code deploys, no waiting on us.

From the Blog

CI/CD integration guides

Deep dives, architecture guides, and practical tutorials for building continuous integration & deployment integrations.

Automating SDLC Evidence: How GRC Platforms Can Stop Chasing Engineers for Screenshots

SOC 2 audits are plagued by manual evidence gathering. Learn how to architect an automated 'Compliance Observer' using Unified APIs to link tickets, PRs, and builds.

Launching: Unified API for CI/CD and Version Control Systems

With our Unified API for CI/CD tools, you can easily integrate popular CI/CD tools like Jenkins, Travis CI, CircleCI, and GitHub CI/CD.

Unified CI/CD API

Start building with the Unified CI/CD API

9 integrations. 11 unified resources. Zero provider-specific code. Ship continuous integration & deployment integrations in hours, not months.

Talk to us