Use this endpoint family to manage stored HTTPS credentials for repositories configured with generic Git Sync providers such as GitLab, Bitbucket, Gitea, Forgejo, Codeberg, and SourceHut. These credentials are scoped to a single repository and are used whenever Code Storage needs to talk to the upstream Git host on your behalf.Documentation Index
Fetch the complete documentation index at: https://code.storage/docs/llms.txt
Use this file to discover all available pages before exploring further.
Create a credential
username is optional. Omit it when your provider accepts a token on its own.
Example:
Request body
Repository ID returned by Create repository.
Username for HTTPS authentication. Optional for token-only providers.
Password or access token for the upstream provider.
Response
Update a credential
Request body
Credential ID returned when the credential was created.
Updated username. Optional.
Updated password or access token.
Response
Delete a credential
Request body
Credential ID to delete.
Response
Returns204 No Content.
Notes
- Create the repository before creating the credential.
- A repository can only have one stored Git credential at a time.
- Credentials are used for generic Git Sync providers, not GitHub App sync.
- After rotating a credential, use Pull from upstream or the next successful push to refresh state.
Error responses
Missing required fields such as
repo_id, id, or password.Repository or credential was not found for the authenticated organization.
A credential already exists for the target repository.