$ brew tap createitv/tap && brew install agc-cli && agc versionMove every release through one red line.
A Go command center for discovering, dry-running, and invoking AppGallery Connect APIs—with stable JSON for people, CI, and coding agents.
$ agc auth check --pretty
{
"data": {
"name": "production",
"mode": "service-account",
"active": true
},
"affordances": {
"next": "agc publishing endpoints"
}
}project profile resolved · dry-run on
Install agc CLI
Use the package manager for your system.
macOS installs through the Createitv Homebrew tap with brew tap createitv/tap && brew install agc-cli. Windows installs through Scoop from the Createitv bucket.
PS> if (!(Get-Command scoop -ErrorAction SilentlyContinue)) { Set-ExecutionPolicy RemoteSigned -Scope CurrentUser -Force; irm get.scoop.sh | iex }; scoop bucket add createitv https://github.com/Createitv/scoop-bucket; scoop install agc-cli; agc versionThe release rail
Context flows forward. Secrets do not.
Each stage owns one job. Credentials remain local, project context remains portable, and destructive API calls require an explicit switch.
AUTH
PS256 / OAuth
PROFILE
project-bound
PACKAGE
upload + status
RELEASE
invoke by choice
Automatic profile binding
Choose once per project. Override only when you mean it.
Bind production in .agc/project.json. Commands resolve the profile in a predictable order, while --profile staging remains available for one-off work.
- 1CLI override
--profile staging - 2Project default
.agc/project.json - 3Active account
~/.agc/credentials.json
{
"appId": "123456789",
"projectId": "987654321",
"packageName": "com.example.app",
"profile": "production"
}Interface registry
Discover the API before writing the request.
Every entry carries its method, path, parameter locations, CLI command, REST route, and dry-run path.
Selected family / publishing
Publishing API
Release metadata, package state, submissions, review withdrawal, and release timing.
agc publishing endpoints --output tableagc publishing status --pretty/api/v1/publishingAll endpoints 14
Expand an endpoint for registered parameters and commands. Consult its reference for full schemas, responses, and permissions.
POST通过下载方式提交软件包add-packageurl/api/publish/v2/app-package-file/by-url
如果您将软件包保存在自己的服务器上,可以直接调用本接口将软件包提交到AppGallery Connect服务器。
Developer-to-Huawei API
| Parameter | Location | Required | Type | Description |
|---|
Parameters are not listed in the registry. See the reference.
Request body: json
Inspect definition
agc publishing add-packageurl --pretty
Local REST definition
/api/v1/publishing/endpoints/add-packageurl
Dry run (supply required parameters first)
agc publishing add-packageurl --invoke --dry-run=true --body body.jsonRead endpoint reference ↗
PUT更新应用文件信息app-file-info/api/publish/v2/app-file-info
图片、视频、APK、RPK、AAB等文件上传完成后,通过该接口刷新应用文件信息。
Developer-to-Huawei API
| Parameter | Location | Required | Type | Description |
|---|
Parameters are not listed in the registry. See the reference.
Request body: json
Inspect definition
agc publishing app-file-info --pretty
Local REST definition
/api/v1/publishing/endpoints/app-file-info
Dry run (supply required parameters first)
agc publishing app-file-info --invoke --dry-run=true --body body.jsonRead endpoint reference ↗
GET查询应用信息app-info-query/api/publish/v2/app-info
此接口用于根据指定语言和应用ID查询应用的详细信息。
Developer-to-Huawei API
| Parameter | Location | Required | Type | Description |
|---|---|---|---|---|
appId | query | Yes | — | Huawei application ID |
lang | query | No | — | Application information language |
Inspect definition
agc publishing app-info-query --pretty
Local REST definition
/api/v1/publishing/endpoints/app-info-query
Dry run (supply required parameters first)
agc publishing app-info-query --invoke --dry-run=trueRead endpoint reference ↗
PUT更新应用基本信息app-info-update/api/publish/v2/app-info
此接口用于更新指定应用的应用详情。
Developer-to-Huawei API
| Parameter | Location | Required | Type | Description |
|---|
Parameters are not listed in the registry. See the reference.
Request body: json
Inspect definition
agc publishing app-info-update --pretty
Local REST definition
/api/v1/publishing/endpoints/app-info-update
Dry run (supply required parameters first)
agc publishing app-info-update --invoke --dry-run=true --body body.jsonRead endpoint reference ↗
POST提交发布app-submit/api/publish/v2/app-submit
此接口用于提交应用审核,调用本接口前必须保证应用信息已补充完整,应用软件包已经上传。
Developer-to-Huawei API
| Parameter | Location | Required | Type | Description |
|---|
Parameters are not listed in the registry. See the reference.
Request body: json
Inspect definition
agc publishing app-submit --pretty
Local REST definition
/api/v1/publishing/endpoints/app-submit
Dry run (supply required parameters first)
agc publishing app-submit --invoke --dry-run=true --body body.jsonRead endpoint reference ↗
POST通过下载方式提交发布app-submit-with-file/api/publish/v2/app-submit-with-file
如果您将软件包保存在自己的服务器上,可以直接调用本接口提交应用审核,并传入软件包的下载地址。
Developer-to-Huawei API
| Parameter | Location | Required | Type | Description |
|---|
Parameters are not listed in the registry. See the reference.
Request body: json
Inspect definition
agc publishing app-submit-with-file --pretty
Local REST definition
/api/v1/publishing/endpoints/app-submit-with-file
Dry run (supply required parameters first)
agc publishing app-submit-with-file --invoke --dry-run=true --body body.jsonRead endpoint reference ↗
GET查询应用包名对应的appidappid-list/api/publish/v2/appid-list
此接口用于根据应用包名查询对应的应用ID,支持一次查询多个应用包名。
Developer-to-Huawei API
| Parameter | Location | Required | Type | Description |
|---|
Parameters are not listed in the registry. See the reference.
Inspect definition
agc publishing appid-list --pretty
Local REST definition
/api/v1/publishing/endpoints/appid-list
Dry run (supply required parameters first)
agc publishing appid-list --invoke --dry-run=trueRead endpoint reference ↗
PUT设置应用GMS依赖属性gms/api/publish/v2/properties/gms
此接口用于向AGC上报应用是否依赖GMS。
Developer-to-Huawei API
| Parameter | Location | Required | Type | Description |
|---|
Parameters are not listed in the registry. See the reference.
Request body: json
Inspect definition
agc publishing gms --pretty
Local REST definition
/api/v1/publishing/endpoints/gms
Dry run (supply required parameters first)
agc publishing gms --invoke --dry-run=true --body body.jsonRead endpoint reference ↗
DELETE删除语言描述信息language-info-delete/api/publish/v2/app-language-info
此接口用于删除指定应用不需要的语言描述信息,默认语言不支持删除。
Developer-to-Huawei API
| Parameter | Location | Required | Type | Description |
|---|
Parameters are not listed in the registry. See the reference.
Inspect definition
agc publishing language-info-delete --pretty
Local REST definition
/api/v1/publishing/endpoints/language-info-delete
Dry run (supply required parameters first)
agc publishing language-info-delete --invoke --dry-run=trueRead endpoint reference ↗
PUT更新语言描述信息language-info-update/api/publish/v2/app-language-info
此接口用于更新指定应用的语言描述信息,如果当前没有语言描述信息则新增。
Developer-to-Huawei API
| Parameter | Location | Required | Type | Description |
|---|
Parameters are not listed in the registry. See the reference.
Request body: json
Inspect definition
agc publishing language-info-update --pretty
Local REST definition
/api/v1/publishing/endpoints/language-info-update
Dry run (supply required parameters first)
agc publishing language-info-update --invoke --dry-run=true --body body.jsonRead endpoint reference ↗
GET查询软件包列表obbfile-package-list/api/publish/v2/package-list
此接口用于查询应用当前关联的软件包列表信息。
Developer-to-Huawei API
| Parameter | Location | Required | Type | Description |
|---|
Parameters are not listed in the registry. See the reference.
Inspect definition
agc publishing obbfile-package-list --pretty
Local REST definition
/api/v1/publishing/endpoints/obbfile-package-list
Dry run (supply required parameters first)
agc publishing obbfile-package-list --invoke --dry-run=trueRead endpoint reference ↗
PUT更新分阶段发布phased-release/api/publish/v2/phased-release
此接口用于将分阶段发布修改为全网发布,或者更新分阶段发布的设置。
Developer-to-Huawei API
| Parameter | Location | Required | Type | Description |
|---|
Parameters are not listed in the registry. See the reference.
Request body: json
Inspect definition
agc publishing phased-release --pretty
Local REST definition
/api/v1/publishing/endpoints/phased-release
Dry run (supply required parameters first)
agc publishing phased-release --invoke --dry-run=true --body body.jsonRead endpoint reference ↗
GET查询软件包编译状态query-aabfile/api/publish/v2/package/compile/status
此接口用于查询软件包的编译状态。
Developer-to-Huawei API
| Parameter | Location | Required | Type | Description |
|---|
Parameters are not listed in the registry. See the reference.
Inspect definition
agc publishing query-aabfile --pretty
Local REST definition
/api/v1/publishing/endpoints/query-aabfile
Dry run (supply required parameters first)
agc publishing query-aabfile --invoke --dry-run=trueRead endpoint reference ↗
PUT更新版本上架时间update-releasetime/api/publish/v2/on-shelf-time
此接口用于设置版本的上架时间。
Developer-to-Huawei API
| Parameter | Location | Required | Type | Description |
|---|
Parameters are not listed in the registry. See the reference.
Request body: json
Inspect definition
agc publishing update-releasetime --pretty
Local REST definition
/api/v1/publishing/endpoints/update-releasetime
Dry run (supply required parameters first)
agc publishing update-releasetime --invoke --dry-run=true --body body.jsonRead endpoint reference ↗
What is agc-cli, and who is it for?
agc-cli is an open-source Go command-line tool for Huawei AppGallery Connect, maintained by Createitv. Its installed command is agc. It organizes API discovery, credential profiles, request previews, and API invocation into reusable commands for HarmonyOS and Huawei app developers who manage app metadata, testers, products, and reports.
Project and guides: GitHub · Usage guide · Issues
Frequently asked questions
Is agc-cli an official Huawei tool?
No. agc-cli is an independent open-source project maintained by Createitv under the MIT license. It organizes endpoints using Huawei AppGallery Connect API references and is not an official Huawei product or support service.
How do I install agc-cli on macOS, Windows, or Linux?
On macOS, run brew tap createitv/tap, then brew install agc-cli. On Windows, run scoop bucket add createitv https://github.com/Createitv/scoop-bucket, then scoop install agc-cli. On Linux, download a binary for your architecture from GitHub Releases. Run agc version to verify installation.
Is agc-cli free, and do I need an account?
agc-cli is free to use and modify under the MIT license. Calling Huawei APIs requires your own AppGallery Connect account, credentials, and permissions. Huawei service pricing and limits remain subject to Huawei terms. Browsing the endpoint reference or inspecting CLI definitions does not require login.
How do I query app information for the first time?
Save credentials with agc auth login --service-account-file ~/.agc/service-account.json --name production, then bind the project with agc init --app-id YOUR_APP_ID --default-profile production. Preview with agc publishing app-info-query --invoke --query appId=YOUR_APP_ID --query lang=en-US. Add --dry-run=false after checking the request. Supply a client_id header explicitly when required.
Are all 156 endpoints production-verified?
No. The registry contains 156 entries across 13 API families; this is registry coverage, not production verification of every endpoint. Registered parameters and command surfaces are shown here. Consult each endpoint reference for full request and response schemas, permissions, and business prerequisites.
Does the default dry run change my app?
No. Endpoint commands with --invoke preview the request without sending it by default. Real invocation requires --dry-run=false. Check the target app, credential profile, and parameters before executing.
Can I use agc-cli with scripts or AI agents?
Yes. JSON output supports script processing. agc capabilities and agc endpoints expose discovery; agc web-server provides local REST routes, and agc openapi exports the contract. Command templates support navigation but do not replace business-state checks or review decisions.
Does a project profile fill all endpoint parameters automatically?
A project configuration can select its default credential profile, with --profile for explicit overrides. App IDs, languages, headers, and request bodies still need to be supplied according to each endpoint. Keep Service Account private keys and credential files out of Git.
Browse the complete API reference by family
Content updated:
Quick start
Three commands to a bound, inspectable workspace.
Use placeholders for your AppGallery Connect values. The second command is what makes the profile automatic for this project.
Save a credential profile
Service Account is the preferred route. Secrets stay in ~/.agc/credentials.json with restricted permissions.
$ agc auth login --service-account-file ~/.agc/service-account.json --name productionBind it to the project
Save project metadata and choose a default credential profile. Supply endpoint parameters explicitly when invoking APIs.
$ agc init --app-id <app-id> --project-id <project-id> --package-name com.example.app --default-profile productionInspect before invoking
Endpoint commands are dry-run first. Review the exact method and URL, then opt into the real request.
$ agc publishing app-info-query --invoke --query appId=<app-id> --dry-run=falseLocal command center
The browser is a window into the same registry.
Start the local REST server when you want live capability data. Without it, this site stays useful as a complete reference surface.
agc web-server --addr :8421/api/v1/capabilitiesfamilies + affordances/api/v1/endpointsall interface entries/api/v1/openapi.jsonmachine-readable contract/api/v1/:family/endpoints/:id/invokedry-run by default