Manage AIQ Repository Configuration with REST APIs
ThisLast isreviewed: September 22, 2026
Use these repository REST APIs only for supported AIQ administration and automation workflows. Treat repository names, branch data, and credentials as sensitive operational configuration.
Recommended guidance
- Use least-privilege accounts or tokens for repository automation.
- Validate API behavior in a
listnon-productionofenvironmentusefulbefore automating changes. - Avoid storing repository
relatedcredentialsRESTorAPIs,tokens in documentation, scripts, or logs.
getRepositoryNamesByUserValidation workflow
Endpoint
- Confirm
therest/preferences/getRepositoryNamesByUser
AIQDescriptionReturnsversion and supported repository API endpoints. - Authenticate with an
arrayapprovedwithaccountalland call read-only endpoints first. - Validate repository
configurationname,namesbranch,fromandcurrentstatusloggedresponsesinbeforeuser.triggeringRequestpullparameters | payloadN/AResponse[ "repoName1", "repoName2", "repoName3" ]
oremptysavearrayoperations. - Log
ifexecutionnoIDsrepoandconfigsnon-sensitiveexists.[ ]getRepositoryByUserEndpointrest/preferences/getRepositoryByUserDescriptionReturns JSON object withresponse detailsofforthe a repo given its name or empty JSON if no configuration with provided name is found.Request parameters | payload?name=repoName1ResponseSuccess{ "proxyPort": 0, "commitMessage": "Appvance Commit", "auth": "Password", "proxyServer": "", "proxyUsername": "", "name": "repoName1", "proxyPassword": "", "proxyType": "defatult", "type": "GIT", "branch": "main", "url": "https://gitlab.com/appvnc/repomemo/", "username": "appvnc"}Error (repoName1 was not found){ }getRepositoryStatusEndpointrest/preferences/getRepositoryStatusDescriptionReturns JSON object with status of the a repo given its name.Request parameters | payload?name=repoName1ResponseSuccess:{ "timeStamp": "2023/01/30 19:59:52", "stack": "", "status": "WORKING"}Error:{ "timeStamp": "0", "stack": "Repository not found", "status": "ERROR"}pullRepositoryEndpointrest/preferences/pullRepositoryDescriptionIf repo is found, it triggers a git pull action on the repotraceability. - Review and
thenrotateexecutescredentialsausedgetRepositoryStatus returning the same JSON as that call.Request parameters | payload?name=repoName1ResponseSuccess:{ "timeStamp": "2023/01/30 19:59:52", "stack": "", "status": "WORKING"}On error:{{ "timeStamp": "2023/01/30 19:59:52", "stack": "Repository not found", "status": "ERROR"}getBranchesEndpointrest/preferences/getBranchesDescriptionReturns the names of all the existing branches in the remote repositoryRequest parameters | payload?name=repoName1ResponseSuccess:{ "timeStamp": "0", "stack": "", "branches": [ "main", "performanceFolder" ], "status": "OK"}On Error:{ "timeStamp": "0", "stack": "Repository not found", "status": "ERROR"}saveRepositoryEndpointrest/preferences/saveRepositoryDescription
integrations.Saves new or updatesby repositoryconfiguration
PossibleNote: errorDelete messages:"Repositoryand withsave givenoperations namecan exists""Incorrect credentials."
Request parameters | payload
{"type":"GIT","name":"repoName1","url":"https://gitlab.net/ac/repo.git","username":"user@example.com","ssh":"","auth":"Password","password":"Wkdz!vxh14x9","branch":"","commitMessage":"","proxyServer":"","proxyPort":0,"proxyUsername":"","proxyPassword":"","proxyType":"defatult"}Response
Success:
{ "message": "Repository successfully saved.", "status": "success"}On Error:
{ "message": "Error: check yourchange repository configuration.", "status":Use "error"}them deleteRepository
with Endpoint
explicit rest/preferences/deleteRepository
Description
Deletes a repository configuration named repoName1 for current user.
Request parameters | payload
?repositoryName=repoName1
Response
Success:
done true
On Error:
intent.done false
Last updated: JulySeptember 07,22, 20232026
If you have any feedback on this topic, please contact us at documentation@appvance.ai.