Coveralls API

Name: Coveralls API API
Brand: Coveralls API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsTesting QaapiKey6 EndpointsREST

For Agents

Register repositories, post test coverage reports from CI, and close parallel build jobs on Coveralls. Use when an agent needs to record code coverage for a build run.

Quickstart

Get started with Coveralls 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:
"post a code coverage report to coveralls"

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

Capabilities

What an agent can do with Coveralls API API.

Post a coverage report for a specific build job, including line and branch coverage data

Retrieve repository configuration details for GitHub, GitLab, or Bitbucket repos already on Coveralls

Update repository settings such as comment behaviour and badge visibility

GET STARTED

Start building with Coveralls API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Coveralls API, keeping it validated and agent-ready. The Coveralls API lets developers and CI systems register repositories, post coverage reports for build jobs, and close out parallel build pipelines that run tests across multiple workers. It is the programmatic surface behind Coveralls' coverage tracking service, accepting LCOV, Cobertura, and other coverage formats from GitHub, GitLab, and Bitbucket projects. The API uses a Personal API Token in the Authorization header and is commonly invoked from CI scripts, custom test runners, and quality dashboards.

Use Cases

Patterns agents use Coveralls API API for, with concrete tasks.

★ CI Coverage Reporting

After a CI build runs the test suite, a coverage tool produces an LCOV or Cobertura report. The job runner then posts that report to Coveralls via POST /api/v1/jobs so that the coverage percentage, line-by-line details, and pull request status checks are updated. This integration takes minutes to set up because most CI providers already have Coveralls plugins, and it keeps the team's coverage history in one place.

Post a coverage report to /api/v1/jobs with service_name 'github-actions', repo_token from the vault, and the LCOV payload, then confirm a 200 response.

Parallel Build Coordination

When a test suite is split across multiple parallel CI workers, each worker posts its partial coverage to Coveralls. Once all workers have submitted their slices, the build coordinator calls POST /webhook with the build number to merge results into a single coverage report. Without this final webhook call, Coveralls leaves the build in an open state and the PR check never resolves.

Send POST /webhook with payload {repo_token, payload: {build_num, status: 'done'}} to close a parallel build for repo 'acme/widgets' once all four workers have posted.

Repository Onboarding Automation

When a new microservice is created from a template, an automation script registers it with Coveralls so coverage tracking is enabled before the first build runs. POST /api/repos creates the entry and returns a repo token that is then injected into the CI environment as COVERALLS_REPO_TOKEN. This avoids manual UI steps and keeps coverage onboarding consistent across hundreds of repos.

Call POST /api/repos with {repo: {service: 'github', name: 'acme/payments-svc'}} and store the returned repo_token as a CI secret named COVERALLS_REPO_TOKEN.

Coverage Quality Gate Agent

An AI agent embedded in a release workflow checks coverage status before merging. It calls GET /api/repos/{service}/{repo_user}/{repo_name} to fetch the current coverage percentage and recent build history, then decides whether to block or approve the merge. Through Jentic, the agent finds the right operation by intent, loads its schema, and executes the call without reading Coveralls documentation.

Search Jentic for 'check coverage status on coveralls', load the GET /api/repos schema, execute against repo 'acme/widgets' on github service, and return the latest coverage_percent.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/api/v1/jobs

Post a coverage report from a CI build

POST

/api/repos

GET

/api/repos/{service}/{repo_user}/{repo_name}

Get repository information

PUT

/api/repos/{service}/{repo_user}/{repo_name}

Update repository settings

DELETE

/api/repos/{service}/{repo_user}/{repo_name}

Delete a repository entry

POST

/webhook

Close a parallel build

POST

/api/v1/jobs

Post a coverage report from a CI build

POST

/api/repos

GET

/api/repos/{service}/{repo_user}/{repo_name}

Get repository information

PUT

/api/repos/{service}/{repo_user}/{repo_name}

Update repository settings

DELETE

/api/repos/{service}/{repo_user}/{repo_name}

Delete a repository entry

Why though Jentic?

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

Credential isolation

Coveralls personal tokens and repo tokens are stored encrypted in the Jentic vault. Agents never see the raw token string — Jentic injects the Authorization header at execution time.

Intent-based discovery

Agents search Jentic with intents like 'post coverage report' or 'register repository on coveralls' and Jentic returns the matching Coveralls operation with its input schema.

Time to first call

Direct Coveralls integration: 2-4 hours for token storage, header formatting, and parallel build webhook handling. Through Jentic: under 15 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Codecov API

Codecov is the main competitor to Coveralls and offers similar coverage upload and reporting endpoints.

Choose Codecov when the team already pays for Codecov or needs its richer pull request comment formatting and component-level coverage rollups.

Alternative

Code Climate API

Code Climate combines coverage tracking with maintainability and technical debt scoring.

Choose Code Climate when coverage alone is not enough and the team also wants code quality and maintainability metrics in the same dashboard.

Complementary

GitHub API

GitHub hosts the source repos that Coveralls tracks and surfaces the coverage status checks on pull requests.

Use GitHub alongside Coveralls when an agent needs to read commit metadata, attach a status check, or comment on a pull request based on the coverage result.

Complementary

CircleCI API

CircleCI runs the build jobs whose coverage is then posted to Coveralls.

Use CircleCI when an agent needs to trigger or inspect the CI build that produces the coverage data being uploaded to Coveralls.

FAQs

Specific to using Coveralls API API through Jentic.

Why is there no official OpenAPI spec for Coveralls API?

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

Coveralls uses a personal API token sent in the Authorization header in the format 'token XXX'. Through Jentic, the token is stored encrypted in the vault and injected at execution time, so the token never appears in the agent's prompt or context.

How do I post a coverage report to Coveralls through Jentic?

Search Jentic for 'post coverage report to coveralls', load the POST /api/v1/jobs schema, then execute with the service name, repo_token, and coverage payload. Jentic handles the Authorization header automatically using the stored personal token.

Can I close a parallel build using the Coveralls API?

Yes. Once all parallel CI workers have posted their partial coverage to /api/v1/jobs, send a POST to /webhook with the build_num and status 'done' so Coveralls merges the slices into one report and resolves the pull request check.

What are the rate limits for the Coveralls API?

Coveralls does not publish hard numerical rate limits in the OpenAPI spec. In practice the API tolerates one report per build job and several repository management calls per minute. If a 429 response appears, back off and retry with exponential delay.

Can I register repositories on Coveralls programmatically?

Yes. POST /api/repos creates a new repository entry and returns a repo_token that you store as the COVERALLS_REPO_TOKEN secret in your CI provider. This is the standard pattern for onboarding many repos at once without using the web UI.