Fisheye Crucible

Name: Fisheye Crucible API
Brand: Fisheye Crucible
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlnone113 EndpointsREST

For Agents

Drive Fisheye and Crucible code reviews, repository browsing, and admin operations across self-hosted Atlassian source-management instances.

Connect the Fisheye Crucible to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Fisheye Crucible, 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 Fisheye Crucible API.

Manage admin groups and the users assigned to them

Configure permission schemes that control repository access

Browse repositories, changesets, and revisions through the rest-service-fecru namespace

Open and update Crucible code reviews and reviewer assignments

GET STARTED

Start building with Fisheye Crucible API

Explore with Jentic

View OpenAPI Document

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

Atlassian Fisheye and Crucible expose an HTTP REST surface for browsing source repositories, running code reviews, and administering project-level access. This OpenAPI spec covers 113 endpoints across the rest-service-fecru namespace, including admin groups, permission schemes, user accounts, repositories, reviews, comments, and changesets. Teams running self-hosted Fisheye or Crucible can drive review workflows, group management, and repository inspection programmatically rather than through the web UI.

Use Cases

Patterns agents use Fisheye Crucible API for, with concrete tasks.

★ Review Workflow Automation on Self-Hosted Atlassian

Engineering teams running self-hosted Fisheye and Crucible automate the creation and routing of code reviews. The rest-service-fecru endpoints let a CI hook open a Crucible review when a feature branch is pushed, attach reviewers from the right admin groups, and update the review state as approvals come in — without manual steps inside the Crucible UI.

When CI completes on a feature branch, call the Crucible review create endpoint with the changeset IDs and the reviewer list pulled from GET /rest-service-fecru/admin/groups/{name}/users.

Permission Scheme Auditing

Security teams audit which permission schemes exist on a Fisheye Crucible instance and which users belong to admin groups that have elevated access. GET /rest-service-fecru/admin/permission-schemes lists the schemes and GET /rest-service-fecru/admin/groups/{name}/users enumerates membership, feeding a quarterly access review into a compliance dashboard.

List every permission scheme via GET /rest-service-fecru/admin/permission-schemes and enumerate user membership for each admin group.

Group Membership Provisioning

When new engineers join, they need to be added to the correct admin and reviewer groups. PUT /rest-service-fecru/admin/groups/{name}/users assigns members and DELETE removes them, so an HRIS-driven script can keep Crucible group membership aligned with current employment without manual sysadmin work.

On HR onboarding event, call PUT /rest-service-fecru/admin/groups/{name}/users to add the new engineer to the engineering reviewer group.

Agent-Driven Review Setup

An AI engineering assistant can use Jentic to discover Fisheye Crucible's review and group endpoints, open a review for a pull request, attach reviewers from the right admin group, and update permissions for a sensitive repository — all through scoped Jentic credentials rather than direct REST calls.

Use Jentic to search 'list fisheye admin groups' and execute GET /rest-service-fecru/admin/groups/ to enumerate the candidate reviewer groups.

Key Endpoints

113 endpoints — atlassian fisheye and crucible expose an http rest surface for browsing source repositories, running code reviews, and administering project-level access.

METHOD

PATH

DESCRIPTION

GET

/rest-service-fecru/admin/groups/

List admin groups

POST

/rest-service-fecru/admin/groups/

Create an admin group

GET

/rest-service-fecru/admin/groups/{name}/users

List users in a group

PUT

/rest-service-fecru/admin/groups/{name}/users

Add users to a group

GET

/rest-service-fecru/admin/permission-schemes

List permission schemes

POST

/rest-service-fecru/admin/permission-schemes

Create a permission scheme

GET

/rest-service-fecru/admin/groups/

List admin groups

POST

/rest-service-fecru/admin/groups/

Create an admin group

GET

/rest-service-fecru/admin/groups/{name}/users

List users in a group

PUT

/rest-service-fecru/admin/groups/{name}/users

Add users to a group

GET

/rest-service-fecru/admin/permission-schemes

List permission schemes

Why though Jentic?

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

Credential isolation

Fisheye Crucible session credentials are stored encrypted in the Jentic vault. Agents receive a scoped reference and Jentic injects the Authorization header per request, so basic-auth credentials never enter agent context.

Intent-based discovery

Agents search by intent (e.g. 'list fisheye admin groups') and Jentic surfaces the matching rest-service-fecru endpoint with its input schema, narrowing 113 paths to the right call.

Time to first call

Direct Fisheye Crucible integration: 2-4 days to read the legacy REST docs and wire up admin and review flows. Through Jentic: a few hours — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Jira

Issue tracker that pairs with Crucible reviews on the same Atlassian stack

Use Jira to track the issue while Fisheye Crucible handles the code-review portion of the same change.

Alternative

GitHub

Cloud-hosted source control and pull-request review platform

Choose GitHub when you can move to cloud hosting and want pull requests instead of Crucible reviews.

Alternative

GitLab

Self-hostable source control with built-in merge request reviews

Choose GitLab when you want a self-hosted DevOps platform that bundles source control and reviews in one product.

FAQs

Specific to using Fisheye Crucible API through Jentic.

What authentication does the Fisheye Crucible API use?

This OpenAPI definition does not declare a security scheme; production Fisheye Crucible instances typically require basic auth or a session cookie configured by the server administrator. Through Jentic the credentials are stored in the vault and injected per request.

Can I manage admin groups with the Fisheye Crucible API?

Yes. GET, POST, PUT, and DELETE on /rest-service-fecru/admin/groups/ and /rest-service-fecru/admin/groups/{name} cover full lifecycle management of admin groups and their members.

What are the rate limits for the Fisheye Crucible API?

Self-hosted Fisheye Crucible does not enforce a documented public rate limit; throughput is bounded by the server's hardware and tomcat thread pool. Stagger bulk operations and monitor server response times when running large jobs.

How do I list permission schemes through Jentic?

Run pip install jentic, search 'list fisheye permission schemes', load GET /rest-service-fecru/admin/permission-schemes, and execute it against your Fisheye Crucible base URL to receive the configured schemes.

Can I add a user to an admin group via this API?

Yes. PUT /rest-service-fecru/admin/groups/{name}/users adds a user to the named admin group and DELETE on the same path removes them.

Does this API support browsing changesets?

The rest-service-fecru namespace exposes repository and changeset endpoints alongside the admin operations covered here, so an integrating service can both browse code history and manage access from the same base URL.