Crucible

Name: Crucible API
Brand: Crucible
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlsession79 EndpointsREST

For Agents

List projects, browse repositories, create code reviews, post review comments, and manage Crucible review lifecycles on a local Crucible instance.

Quickstart

Get started with Crucible 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:
"create a Crucible code review"

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

Capabilities

What an agent can do with Crucible API.

List projects and repositories on the Crucible instance

Browse repository content, change history, and individual revisions

Create code reviews and attach changesets, files, or patches to a review

Post general or line-anchored comments on a review and reply within threads

Filter and search reviews with details, including by repository or saved filter

GET STARTED

Start building with Crucible API

Explore with Jentic

View OpenAPI Document

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

Crucible is Atlassian's on-premise code review product, used by teams that hold their source control inside the firewall. The REST API exposes 79 endpoints across project listing, repository browsing, and the full code-review lifecycle including creating reviews, attaching changesets, files, and patches, posting general or line-anchored comments, and closing reviews. Authentication runs through the /rest-service/auth-v1/login endpoint, which establishes a session for subsequent calls.

Use Cases

Patterns agents use Crucible API for, with concrete tasks.

★ Automated Review Creation from CI

Open a Crucible review automatically when a CI build attaches the relevant changeset by calling POST /rest-service/reviews-v1 to create the review and POST /rest-service/reviews-v1/{id}/addChangeset to attach the changes. Engineering teams using Crucible alongside an on-prem build pipeline use this so every release branch produces a review record without a developer creating it by hand. POST /rest-service/reviews-v1/{id}/close finishes it once approvals land.

Create a Crucible review titled 'Release 2.4 hotfix' and attach changeset CR-1234 to it via /addChangeset

Review Comment Aggregation

Pull every review's comments into a reporting database by listing reviews via /rest-service/reviews-v1/filter, then calling /rest-service/reviews-v1/{id}/comments per review. Engineering management teams use this to surface review velocity, blockers, and outstanding comment threads without depending on the Crucible UI.

List reviews matching the 'open' filter and pull every comment from each via /reviews-v1/{id}/comments

Repository Browsing and History

Surface repository content and change history outside Crucible's UI by calling /rest-service/repositories-v1/browse/{repository}/{path}, /content/{repository}/{revision}/{path}, and /history/{repository}/{revision}/{path}. This is useful when integrating Crucible's view of the source tree into another tool or chat surface.

Browse the contents of repository core at path src/main/java and list the files at HEAD

AI Agent Review Triage

An AI agent triages a backlog of open Crucible reviews through Jentic. The agent searches for the crucible_filter_reviews operation, executes against the user's vaulted Crucible session credentials, and produces a ranked list of reviews most in need of attention based on age, comment count, and reviewer load. Jentic isolates the session credential so the agent never sees the raw login.

Use the Jentic SDK to log in to Crucible, list open reviews, and rank them by oldest unanswered comment

Key Endpoints

79 endpoints — crucible is atlassian's on-premise code review product, used by teams that hold their source control inside the firewall.

METHOD

PATH

DESCRIPTION

POST

/rest-service/auth-v1/login

Establish a Crucible session

POST

/rest-service/reviews-v1

Create a new code review

POST

/rest-service/reviews-v1/{id}/addChangeset

Attach a changeset to a review

POST

/rest-service/reviews-v1/{id}/addFile

Attach a file to a review

POST

/rest-service/reviews-v1/{id}/comments

Why though Jentic?

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

Credential isolation

Crucible username and password are held encrypted in the Jentic vault. Agents receive a scoped execution token and Jentic handles the /rest-service/auth-v1/login exchange and session reuse so the raw credentials never enter the agent's context.

Intent-based discovery

Agents search Jentic with intents like 'create a Crucible review' or 'list open reviews' and Jentic returns the matching Crucible operation with its input schema, removing the need to read the Crucible REST docs.

Time to first call

Direct Crucible integration: 1-2 days for session login plumbing and matching the on-prem base URL to your environment. Through Jentic: under half a day — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

crowd.dev API

crowd.dev tracks community contributions while Crucible handles internal code review on the same codebase

Use crowd.dev to log external contributor activity and Crucible to manage the formal review of those contributions when they land in an internal repo.

Complementary

Cronitor API

Cronitor monitors scheduled jobs that may sync Crucible review data to a reporting warehouse

Pair Cronitor with Crucible to verify a recurring review-comment export job actually fired.

Complementary

Cron-job.org API

cron-job.org schedules recurring HTTP calls that can drive Crucible review-list polling

Use cron-job.org to schedule a recurring Crucible reviews-v1/filter poll when an agent doesn't host its own scheduler.

FAQs

Specific to using Crucible API through Jentic.

What authentication does the Crucible API use?

Crucible uses session-based authentication. Clients call POST /rest-service/auth-v1/login with username and password and reuse the resulting session cookie on subsequent requests. Through Jentic the username and password are held encrypted in the vault and Jentic handles the login exchange so the agent never sees the credentials.

Can I create a code review through the API?

Yes. POST /rest-service/reviews-v1 creates a review, and follow-up calls to /rest-service/reviews-v1/{id}/addChangeset, /addFile, or /addPatch attach the actual code under review. POST /rest-service/reviews-v1/{id}/close ends the review once it is approved.

How do I filter reviews by repository or status?

GET /rest-service/reviews-v1/filter accepts filter parameters and returns matching reviews; /filter/{filter} returns the reviews under a saved filter, and /search/{repository} narrows by repository. The /details variants return enriched review payloads.

How do I create a review through Jentic?

Search Jentic for 'create a Crucible review', load the operation schema for POST /rest-service/reviews-v1, and execute with the project key, title, and reviewer list. Jentic handles the login session so the agent doesn't need to manage cookies.

How many endpoints does the Crucible API expose?

Seventy-nine endpoints across authentication, projects, repository browsing, reviews, review actions and comments, and review search and filter operations.

Can I post a comment on a specific line of a review?

Yes. POST /rest-service/reviews-v1/{id}/comments creates a comment, and the /comments/versioned endpoint exposes file-and-line-anchored comments so an agent can attach feedback to specific code lines.