Modify multiple files in a repository
const url = 'https://gitea.com/api/v1/repos/example/example/contents';const options = { method: 'POST', headers: {Authorization: 'Basic <credentials>', 'Content-Type': 'application/json'}, body: '{"author":{"email":"hello@example.com","name":"example"},"branch":"example","committer":{"email":"hello@example.com","name":"example"},"dates":{"author":"2026-04-15T12:00:00Z","committer":"2026-04-15T12:00:00Z"},"files":[{"content":"example","from_path":"example","operation":"create","path":"example","sha":"example"}],"force_push":true,"message":"example","new_branch":"example","signoff":true}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://gitea.com/api/v1/repos/example/example/contents \ --header 'Authorization: Basic <credentials>' \ --header 'Content-Type: application/json' \ --data '{ "author": { "email": "hello@example.com", "name": "example" }, "branch": "example", "committer": { "email": "hello@example.com", "name": "example" }, "dates": { "author": "2026-04-15T12:00:00Z", "committer": "2026-04-15T12:00:00Z" }, "files": [ { "content": "example", "from_path": "example", "operation": "create", "path": "example", "sha": "example" } ], "force_push": true, "message": "example", "new_branch": "example", "signoff": true }'Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Owner of the repo
Name of the repo
Request Bodyrequired
Section titled “Request Bodyrequired”ChangeFilesOptions options for creating, updating or deleting multiple files
Note: author and committer are optional (if only one is given, it will be used for the other, otherwise the authenticated user will be used)
object
Identity for a person’s identity like an author or committer
object
Email is the person’s email address
Name is the person’s name
Branch (optional) is the base branch for the changes. If not supplied, the default branch is used
Identity for a person’s identity like an author or committer
object
Email is the person’s email address
Name is the person’s name
CommitDateOptions store dates for GIT_AUTHOR_DATE and GIT_COMMITTER_DATE
object
Author is the author date for the commit
Committer is the committer date for the commit
List of file operations
ChangeFileOperation for creating, updating or deleting a file
object
New or updated file content, it must be base64 encoded
Old path of the file to move
Indicates what to do with the file: “create” for creating a new file, “update” for updating an existing file, “upload” for creating or updating a file, “rename” for renaming a file, and “delete” for deleting an existing file.
Path to the existing or new file
The blob ID (SHA) for the file that already exists, required for changing existing files
Force_push (optional) will do a force-push if the new branch already exists
Message (optional) is the commit message of the changes. If not supplied, a default message will be used
New_branch (optional) will make a new branch from base branch for the changes. If not supplied, the changes will be committed to the base branch
Add a Signed-off-by trailer by the committer at the end of the commit log message.
Responses
Section titled “Responses”FilesResponse
FilesResponse contains information about multiple files from a repo
object
object
object
Date is the commit date in string format
Email is the person’s email address
Name is the person’s name
object
Date is the commit date in string format
Email is the person’s email address
Name is the person’s name
Created is the time when the commit was created
HTMLURL is the web URL for viewing this commit
Message is the commit message
Parents contains parent commit metadata
object
Created is the time when the commit was created
SHA is the commit SHA hash
URL is the API URL for the commit
SHA is the commit SHA hash
object
Created is the time when the commit was created
SHA is the commit SHA hash
URL is the API URL for the commit
URL is the API URL for the commit
Files contains the list of file contents and metadata
ContentsResponse contains information about a repo’s entry’s (dir, file, symlink, submodule) metadata and content
object
FileLinksResponse contains the links for a repo’s file
object
GitURL is the Git API URL for this file
HTMLURL is the web URL for this file
Self is the API URL for this file
content is populated when type is file, otherwise null
DownloadURL is the direct download URL for this file
encoding is populated when type is file, otherwise null
GitURL is the Git API URL for this blob or tree
HTMLURL is the web URL for this file or directory
LastCommitMessage is the message of the last commit that affected this file
LastCommitSHA is the SHA of the last commit that affected this file
LfsOid is the Git LFS object ID if this file is stored in LFS
LfsSize is the file size if this file is stored in LFS
mode is the Git file mode as an octal string, e.g. 100644 (regular), 100755 (executable), 120000 (symlink), 160000 (submodule)
Name is the file or directory name
Path is the full path to the file or directory
SHA is the Git blob or tree SHA
Size is the file size in bytes
submodule_git_url is populated when type is submodule, otherwise null
target is populated when type is symlink, otherwise null
type will be file, dir, symlink, or submodule
URL is the API URL for this file or directory
PayloadCommitVerification represents the GPG verification of a commit
object
The signed payload content
The reason for the verification status
The GPG signature of the commit
PayloadUser represents the author or committer of a commit
object
Full name of the commit author
Username of the user
Whether the commit signature is verified
Examplegenerated
{ "commit": { "author": { "date": "example", "email": "hello@example.com", "name": "example" }, "committer": { "date": "example", "email": "hello@example.com", "name": "example" }, "created": "2026-04-15T12:00:00Z", "html_url": "https://example.com", "message": "example", "parents": [ { "created": "2026-04-15T12:00:00Z", "sha": "example", "url": "https://example.com" } ], "sha": "example", "tree": { "created": "2026-04-15T12:00:00Z", "sha": "example", "url": "https://example.com" }, "url": "https://example.com" }, "files": [ { "_links": { "git": "example", "html": "example", "self": "example" }, "content": "example", "download_url": "https://example.com", "encoding": "example", "git_url": "https://example.com", "html_url": "https://example.com", "last_author_date": "2026-04-15T12:00:00Z", "last_commit_message": "example", "last_commit_sha": "example", "last_committer_date": "2026-04-15T12:00:00Z", "lfs_oid": "example", "lfs_size": 1, "mode": "example", "name": "example", "path": "example", "sha": "example", "size": 1, "submodule_git_url": "https://example.com", "target": "example", "type": "example", "url": "https://example.com" } ], "verification": { "payload": "example", "reason": "example", "signature": "example", "signer": { "email": "hello@example.com", "name": "example", "username": "example" }, "verified": true }}APIError is error format response
Headers
Section titled “Headers”APINotFound is a not found empty response
APIError is error format response
Headers
Section titled “Headers”APIRepoArchivedError is an error that is raised when an archived repo should be modified