CodeScene Public API

Name: CodeScene Public API API
Brand: CodeScene Public API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilitybearer42 EndpointsREST

For Agents

Run and read CodeScene project analyses, technical debt, code health, and developer statistics for engineering productivity reporting.

Quickstart

Get started with CodeScene Public API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get the latest CodeScene project analysis"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with CodeScene Public API API.

Trigger a fresh analysis on a CodeScene project via POST /projects/{projectId}/run-analysis

Read the latest project analysis with GET /projects/{projectId}/analyses/latest, including code health and component breakdown

Pull delta analysis results for pull request gating via GET /projects/{projectId}/delta-analyses/{deltaAnalysisId}

Inspect technical debt friction by component via GET /projects/{projectId}/analyses/{analysisId}/technical-debt

GET STARTED

Start building with CodeScene Public API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for CodeScene Public API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for CodeScene Public API, keeping it validated and agent-ready. CodeScene is a behavioural code analysis platform that combines code health scoring with author and team statistics, technical debt heatmaps, delta analyses on pull requests, and code coverage gating. The v2 API exposes 42 endpoints over api.codescene.io covering projects, repositories, full and delta analyses, components, files, commits, issues, technical debt, code coverage, and developer or team settings. Authentication is a Bearer token created in the CodeScene UI.

Use Cases

Patterns agents use CodeScene Public API API for, with concrete tasks.

★ Pull Request Risk Gating with Delta Analysis

Run CodeScene's delta analysis on every pull request and gate merges on the resulting risk score. The agent calls GET /projects/{projectId}/delta-analyses to find the analysis matching a PR commit, reads the score, and posts a status check back to the SCM. Catches risky changes before they land instead of after a postmortem.

Find the delta analysis for commit abc123, read the risk score, and if it exceeds 7 post a failing status check on the corresponding GitHub pull request

Technical Debt Heatmap for Refactoring

Generate a technical debt heatmap by reading GET /projects/{projectId}/analyses/{analysisId}/technical-debt and joining it with file-level data. The agent ranks components and files by friction score so a refactoring sprint targets the highest-leverage areas. Replaces gut-feel debate about where to invest engineering time.

Pull the latest analysis id, then call GET /projects/{projectId}/analyses/{analysisId}/technical-debt and produce a top-10 list of components by friction

Engineering Productivity Reporting

Build an engineering productivity report from CodeScene's author and branch statistics. The agent reads GET /projects/{projectId}/analyses/{analysisId}/author-statistics and GET /projects/{projectId}/analyses/{analysisId}/branch-statistics to produce metrics on contributor count, knowledge concentration, and delivery cadence. Powers monthly reviews without manual chart-building.

For project 'platform' fetch author-statistics for the latest analysis and email a CSV ranked by lines-changed-last-30-days

Code Coverage Gate Monitoring

Use the code coverage gate-results endpoints to track whether builds are meeting coverage targets across a portfolio. The agent calls GET /code-coverage/projects/{projectId}/gate-results/outcomes per project and flags any gate that failed in the last 24 hours. Keeps coverage commitments honest without each team having to surface their own status.

For every project list outcomes via GET /code-coverage/projects/{projectId}/gate-results/outcomes for the last 24h and post any failed gates to a Slack channel

Agent-Driven CodeScene Lookups via Jentic

An agent connected to Jentic can answer 'how healthy is the payments service?' by triggering a fresh analysis or reading the latest one without holding the raw API token. Jentic stores the CodeScene Bearer token in its vault and exposes the operations through intent search so the agent can search, load, and execute in seconds.

Search Jentic for 'get latest CodeScene analysis', load the GET /projects/{projectId}/analyses/latest schema, execute it for the payments project, and return the headline code health score

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/projects

List CodeScene projects

POST

/projects/new

Create a new project

POST

/projects/{projectId}/run-analysis

Trigger an analysis

GET

/projects/{projectId}/analyses/latest

Get the latest analysis

GET

/projects/{projectId}/analyses/{analysisId}/technical-debt

Get technical debt friction

GET

/projects/{projectId}/delta-analyses/{deltaAnalysisId}

Get delta analysis details

GET

/projects/{projectId}/analyses/{analysisId}/author-statistics

Get author statistics

GET

/code-coverage/projects/{projectId}/gate-results/outcomes

Get code coverage gate outcomes

GET

/projects

List CodeScene projects

POST

/projects/new

Create a new project

POST

/projects/{projectId}/run-analysis

Trigger an analysis

GET

/projects/{projectId}/analyses/latest

Get the latest analysis

GET

/projects/{projectId}/analyses/{analysisId}/technical-debt

Get technical debt friction

Why though Jentic?

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

Credential isolation

CodeScene Bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped execution access; the raw token never enters agent context, and rotation can be handled centrally.

Intent-based discovery

Agents search Jentic by intent (e.g., 'get CodeScene technical debt') and Jentic returns the matching operation with parameter schema, so the agent can call the right /projects/{projectId}/analyses/... endpoint without scraping vendor docs.

Time to first call

Direct CodeScene integration: 1-2 days to model projects, analyses, and developer settings and wire Bearer auth. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

SonarCloud API

Static analysis platform with code quality and security rules running in the cloud

Choose SonarCloud for rule-based static analysis; CodeScene is stronger for behavioural and team-level signals

Alternative

Code Climate Quality API

Maintainability and issue tracking with comparable file-level metrics

Choose Code Climate for simpler maintainability scores; choose CodeScene when delta analysis and author behavioural data are needed

Complementary

GitHub API

Pair with CodeScene to post analysis-derived status checks and comments on pull requests

Use when an agent reads CodeScene results and acts on them inside GitHub

FAQs

Specific to using CodeScene Public API API through Jentic.

Why is there no official OpenAPI spec for CodeScene Public API?

CodeScene does not publish a public OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CodeScene Public 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 CodeScene Public API use?

The CodeScene Public API uses HTTP Bearer authentication. Create an API token inside the CodeScene UI and send it as Authorization: Bearer {token}. Through Jentic the token is stored in the vault and never enters agent context.

Can I trigger an analysis through the CodeScene API?

Yes. POST /projects/{projectId}/run-analysis kicks off a fresh analysis for the specified project. The endpoint is asynchronous, so poll GET /projects/{projectId}/analyses/latest until the new analysis id appears with a completed status.

What are the rate limits for the CodeScene Public API?

CodeScene does not publish a fixed public rate limit, and limits depend on plan tier. Treat the API as best-effort and back off on HTTP 429 responses. For portfolio-wide reporting, throttle requests and rely on the latest analysis cache rather than triggering new runs each call.

How do I read delta analysis results for a pull request through Jentic?

Search Jentic for 'get CodeScene delta analysis', load the GET /projects/{projectId}/delta-analyses/{deltaAnalysisId} schema, and execute it with the relevant ids. Jentic injects the Bearer token from the vault and returns the parsed risk score and detail.

Does the CodeScene Public API include code coverage data?

Yes. The /code-coverage endpoints expose stored coverage data as well as gate-result outcomes and insights at /code-coverage/projects/{projectId}/gate-results/. The data is uploaded by CI integrations rather than pulled live from a coverage tool.