AWS CodeCommit

Name: AWS CodeCommit API
Brand: AWS CodeCommit
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlhmac77 EndpointsREST

For Agents

Manage AWS CodeCommit repositories, branches, commits, files, pull requests, and approval rule templates through 77 endpoints — covering Git workflows that don't need a local clone.

Connect the AWS CodeCommit to your agent

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

Create, describe, and delete CodeCommit repositories with cross-account permissions

Create branches, commits, and individual file changes via API rather than git push

Open pull requests, post comments, approve, and merge with squash, fast-forward, or three-way strategies

Define approval rule templates and associate them with repositories for required reviewers

GET STARTED

Start building with AWS CodeCommit API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for AWS CodeCommit, keeping it validated and agent-ready. AWS CodeCommit is a managed Git source-control service that runs entirely inside an AWS account. The API exposes 77 operations covering repositories, branches, commits, files, pull requests, approval rule templates, and merge conflict inspection, so an agent can create branches, open and merge pull requests, and audit repository activity without using a Git client.

Use Cases

Patterns agents use AWS CodeCommit API for, with concrete tasks.

★ Programmatic Pull Request Workflow

Tooling teams use CreatePullRequest, PostCommentForPullRequest, UpdatePullRequestApprovalState, and MergePullRequestBySquash to drive the entire review lifecycle without a Git client. ListPullRequests filters by repository, author, and status so an agent can audit open work or auto-merge ready PRs that satisfy approval rules. This is the path of least resistance when running review automation inside AWS without external CI.

Open a pull request from branch feature/login to branch main in repository web-app, then post the description from the linked Jira ticket as a comment

API-Driven File Edits in a Repository

When an agent needs to update a config file across many repos (for example, a renovate-style dependency bump), CreateCommit and PutFile let it write changes without cloning. The API takes branch, parent commit ID, and a file blob, then returns the new commit ID. Combined with CreateBranch and CreatePullRequest, this enables fully unattended fleet-wide refactors.

Create a commit on branch chore/bump-deps in repository api-service that updates package.json to version 2.4.0 and opens a PR against main

Approval Rule Governance Across Repositories

Platform teams enforce review standards by creating approval rule templates with CreateApprovalRuleTemplate and applying them with BatchAssociateApprovalRuleTemplateWithRepositories. The rule sets minimum approver counts and approver pools, so production repositories require two reviewers automatically. This is faster than configuring GitHub branch protection per repo when the source of truth lives in AWS.

Create an approval rule template requiring two members of the platform-leads pool, then associate it with all repositories tagged Tier=production

AI Agent Integration via Jentic

Through Jentic, an AI agent uses CodeCommit by searching for an intent like 'open a CodeCommit pull request', loading the CreatePullRequest schema, and executing the call with source and destination references. Jentic signs the SigV4 request server-side using IAM credentials in the MAXsystem vault.

Search Jentic for 'open a CodeCommit pull request', load the CreatePullRequest schema, and execute it with source feature/x, destination main, and a generated description

Key Endpoints

77 endpoints — jentic publishes the only available openapi specification for aws codecommit, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=CodeCommit_20150413.CreateRepository

Create a new Git repository

POST

/#X-Amz-Target=CodeCommit_20150413.CreateBranch

Create a branch in a repository

POST

/#X-Amz-Target=CodeCommit_20150413.CreateCommit

Create a commit with file changes

POST

/#X-Amz-Target=CodeCommit_20150413.CreatePullRequest

Open a pull request between branches

POST

/#X-Amz-Target=CodeCommit_20150413.CreateApprovalRuleTemplate

Define an approval rule template

POST

/#X-Amz-Target=CodeCommit_20150413.AssociateApprovalRuleTemplateWithRepository

Apply an approval rule template to a repository

POST

/#X-Amz-Target=CodeCommit_20150413.DescribeMergeConflicts

Describe merge conflicts between branches

POST

/#X-Amz-Target=CodeCommit_20150413.CreateRepository

Create a new Git repository

POST

/#X-Amz-Target=CodeCommit_20150413.CreateBranch

Create a branch in a repository

POST

/#X-Amz-Target=CodeCommit_20150413.CreateCommit

Create a commit with file changes

POST

/#X-Amz-Target=CodeCommit_20150413.CreatePullRequest

Open a pull request between branches

POST

/#X-Amz-Target=CodeCommit_20150413.CreateApprovalRuleTemplate

Define an approval rule template

Why though Jentic?

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

Credential isolation

AWS access key ID and secret are stored encrypted in the Jentic MAXsystem vault. Agents call CodeCommit via Jentic, which signs each request with SigV4 server-side — raw IAM credentials and Git credentials never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g. 'open a CodeCommit pull request' or 'create a commit on a branch') and Jentic returns the matching CodeCommit operation with its input schema, so the agent calls CreatePullRequest or CreateCommit directly without browsing the AWS docs.

Time to first call

Direct AWS SDK integration: 1-3 days for SigV4, IAM, Git credential handling, and approval rule logic. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

GitHub

GitHub provides Git hosting plus an ecosystem of CI, code review, and collaboration tooling

Choose GitHub when the agent needs the broader ecosystem (Actions, Copilot, public OSS) rather than IAM-scoped private repos.

Alternative

GitLab

GitLab offers integrated Git hosting, CI/CD, and security scanning in one product

Choose GitLab when the agent needs CI/CD and security scanning bundled with source control.

Complementary

AWS CodePipeline

CodePipeline triggers builds and deployments from CodeCommit branch and PR events

Use CodePipeline when the agent needs to wire CodeCommit changes into a multi-stage release pipeline.

FAQs

Specific to using AWS CodeCommit API through Jentic.

Why is there no official OpenAPI spec for AWS CodeCommit?

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

CodeCommit uses AWS Signature Version 4 (HMAC) signed requests with an IAM access key and secret. Git over HTTPS uses Git credentials generated from IAM, while the management API used here uses raw SigV4. Through Jentic, the SigV4 signature is computed server-side from credentials in the MAXsystem vault.

Can I create a commit through the API without cloning the repository?

Yes. CreateCommit takes the repository name, target branch, parent commit ID, and an array of putFiles or deleteFiles entries with file content. It creates the commit on the branch tip and returns the new commit ID, so the agent can open a PR without a local Git working copy.

How do I open and merge a CodeCommit pull request from the API?

Call CreatePullRequest with sourceReference, destinationReference, and a title, then call MergePullRequestBySquash, MergePullRequestByFastForward, or MergePullRequestByThreeWay with the pull request ID. Approval rules attached to the repository must be satisfied first or the merge call returns PullRequestApprovalRulesNotSatisfiedException.

What are the rate limits for the AWS CodeCommit API?

AWS enforces per-account, per-region throttling on CodeCommit; data-plane operations like CreateCommit return ThrottlingException when limits are exceeded. The AWS SDKs that Jentic wraps implement exponential backoff automatically.

How do I open a pull request through Jentic with an AI agent?

Run pip install jentic, then have the agent search for 'open a CodeCommit pull request', load the CreatePullRequest schema, and execute it with the source branch, destination branch, and title. Use PostCommentForPullRequest to add review notes, then MergePullRequestBySquash to land the change.