Create Git Credential

Create a stored HTTPS credential for a repository configured with a generic Git upstream.

JWT claims

Required scopes: repo:write
Requires per repo scope: Yes

POST /api/repos/{repo_name}/git-credentials

Create Git Credential

cURL

curl --request POST \
  --url https://api.{cluster}.code.storage/api/repos/{repo_name}/git-credentials \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "password": "glpat_xxxxxxxxxxxx",
  "username": "git"
}
'

201

{
  "created_at": "2026-03-12T15:04:05Z",
  "id": "ggc_1234567890abcdef"
}

Authorizations

Authorization · string · header · required

JWT bearer token signed with your organization's registered signing key. There is no OAuth authorization server; you mint tokens yourself and the token's scopes claim carries the granted permission scopes. Public scopes: git:read (read repository contents), git:write (write branches, commits, tags, and notes), repo:write (create and manage repositories), org:read (list an organization's repositories). Each operation's security requirement names the scopes it requires. See https://code.storage/docs/getting-started/authentication for how to mint tokens.

Path Parameters

repo_name · string · required

Repository name. Names that contain / or any other character that is not safe in a URL path segment must be URL encoded so the value occupies a single path segment. For example pierre/example is sent as pierre%2Fexample. Plain names such as example can be sent as-is. The server URL-decodes the value before resolving the repository.

Body

application/json

Store HTTPS credentials for a generic Git upstream such as GitLab, Bitbucket, Gitea, Forgejo, Codeberg, or SourceHut.

Request body for storing a new HTTPS Git credential when the repository is identified via the URL path.

password · string · required

Password or access token for the upstream provider.

Example:

"glpat_xxxxxxxxxxxx"

username · string · required

Optional username for HTTPS authentication. Omit it for token-only providers.

Example:

"git"

Response

201

application/json

Credential created successfully.

Stored Git credential summary returned after a credential is created or updated.

id · string · required

Credential ID returned when the credential is created.

Example:

"ggc_1234567890abcdef"

created_at · string

Credential creation timestamp in ISO 8601 format.

Example:

"2026-03-12T15:04:05Z"