Codebase API

Name: Codebase API API
Brand: Codebase API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlbasic9 EndpointsREST

For Agents

List, create, update, and delete Codebase projects and repositories using HTTP Basic authentication. Suitable for agents managing source-controlled work on the Codebase platform.

Quickstart

Get started with Codebase 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:
"manage a Codebase project repository"

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

Capabilities

What an agent can do with Codebase API API.

List every project in a Codebase account via GET /projects

Create a new Codebase project with POST /create_project

Update an existing project's metadata using PUT /project/{projectId}

Provision Git, Mercurial, or Subversion repositories inside a project via POST /{project}/repositories

GET STARTED

Start building with Codebase API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Codebase API, keeping it validated and agent-ready. Codebase is a project management and source code hosting service that combines Git, Mercurial, and Subversion repository hosting with ticket tracking, time tracking, and notebook tools. The Codebase API exposes 9 endpoints for managing projects and repositories, using HTTP Basic authentication with an account name plus a 40-character API key. Request and response bodies are XML, and the API targets teams that need a self-contained alternative to combining GitHub or GitLab with a separate issue tracker.

Use Cases

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

★ Project Provisioning for New Engagements

Spin up a Codebase project and one or more repositories whenever a new client engagement begins. The API lets you call POST /create_project followed by POST /{project}/repositories so the engineering team has source control and ticketing in place from day one. Useful for agencies and consultancies that need repeatable project bootstrapping without manual UI clicks.

Call POST /create_project with name 'Acme Mobile App' then POST /{project}/repositories to add a Git repository named 'mobile-app' and return both clone URLs

Repository Inventory and Audit

Build a current inventory of every repository across every Codebase project for security, licensing, or migration audits. Iterate GET /projects then GET /{project}/repositories per project to produce a structured list. Keeps account-wide visibility honest when projects accumulate over years.

Call GET /projects and for each returned project call GET /{project}/repositories, then output a CSV of project name, repository name, and SCM type

Decommissioning Old Projects

When a client engagement ends or a product is sunset, remove the project and its repositories cleanly. The API supports DELETE /{project} and DELETE /{project}/{repository} so that decommissioning can be scripted alongside backup steps. This avoids paying for inactive seats and reduces the attack surface of forgotten repos.

For project 'legacy-portal' fetch its repositories with GET /{project}/repositories, archive each via local clone, then DELETE /{project}/{repository} for each followed by DELETE /{project}

Migration Off Codebase

Codebase customers occasionally migrate to GitHub or GitLab. The API lets agents read the project list, enumerate repositories, and capture clone URLs so an automated migration tool can mirror each repository into the new host. Migration windows shrink from days of manual work to a single scripted run.

Iterate every project and repository, mirror each via git clone --mirror against the Codebase clone URL, then push each to a matching GitHub repository created via the GitHub API

Agent-Driven Repository Management via Jentic

An AI agent connected to Jentic can manage Codebase projects and repositories without holding the raw API key. The agent searches Jentic for 'manage Codebase repository', loads the operation schema, and executes calls against api3.codebasehq.com while Jentic injects HTTP Basic credentials from the vault. End users can issue natural-language instructions and the agent performs the right combination of project and repository operations.

Use Jentic to search 'create a Codebase project', load the POST /create_project schema, and execute it for project name 'AI Pilot' on behalf of the requesting user

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/projects

List all projects in the Codebase account

POST

/create_project

Create a new project

GET

/{project}

Retrieve a specific project

PUT

/project/{projectId}

Update an existing project

DELETE

/{project}

Delete a project

GET

/{project}/repositories

List repositories under a project

POST

/{project}/repositories

Create a repository inside a project

DELETE

/{project}/{repository}

Delete a repository

GET

/projects

List all projects in the Codebase account

POST

/create_project

Create a new project

GET

/{project}

Retrieve a specific project

PUT

/project/{projectId}

Update an existing project

DELETE

/{project}

Delete a project

GET

Why though Jentic?

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

Credential isolation

Codebase HTTP Basic credentials (account_name/username plus 40-character API key) are stored encrypted in the Jentic vault. Agents receive scoped execution access; the raw API key never enters agent context or logs.

Intent-based discovery

Agents search Jentic by intent (e.g., 'create a Codebase repository') and Jentic returns the matching operation with its parameter schema, so the agent can call POST /{project}/repositories without scraping vendor docs.

Time to first call

Direct Codebase integration: 1-2 days to wire HTTP Basic auth, XML parsing, and error handling. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

GitHub API

Far larger ecosystem and richer endpoints for repositories, pull requests, and issues than Codebase

Choose GitHub when the team wants the broadest tooling integrations and JSON responses; Codebase suits teams already invested in its ticket and time-tracking workflow

Alternative

GitLab API

Self-hostable Git platform with built-in CI/CD that competes directly with Codebase's all-in-one positioning

Choose GitLab when CI/CD pipelines are part of the same workflow as repository hosting

Complementary

Atlassian Jira API

Use Jira for richer issue tracking while Codebase hosts the underlying repositories

Pair with Codebase when the customer's project management lives in Jira but source control stays in Codebase

FAQs

Specific to using Codebase API API through Jentic.

Why is there no official OpenAPI spec for Codebase API?

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

The Codebase API uses HTTP Basic authentication. The username is in the form account_name/username and the password is a 40-character API key generated in the Codebase account profile. Through Jentic, the credential is stored in the vault and never enters the agent's context.

Can I create Git repositories programmatically with the Codebase API?

Yes. POST /{project}/repositories creates a new repository inside a parent project, and the spec supports Git, Mercurial, and Subversion repository types. The project must already exist, so you typically pair this call with POST /create_project for net-new engagements.

What are the rate limits for the Codebase API?

Codebase does not publish a public rate limit in its documentation. Treat the API as best-effort and back off on HTTP 429 or 503 responses. For batch jobs such as account-wide repository inventories, throttle to a few requests per second to stay safe.

How do I list all repositories in a project through Jentic?

Search Jentic for 'list Codebase repositories', load the GET /{project}/repositories schema, and execute it with the project shortname. Jentic injects the HTTP Basic credential from the vault, parses the XML response, and returns repository metadata to the agent.

Does the Codebase API return JSON?

No. Request and response bodies are XML. Agents calling through Jentic receive parsed structured data, but if you call the API directly you must serialise and deserialise XML payloads yourself.