AppGallery Connect, mapped for the terminal

Move 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.

Get started Browse 156 interfaces

13 API families156 registered interfaces3 output formats

agc / productionreference mode

One command surface. Your workflow.

AUTHPS256 / OAuth

PROFILEproject-bound

PACKAGEupload + status

RELEASEinvoke by choice

$ agc auth check --pretty

{
  "data": {
    "name": "production",
    "mode": "service-account",
    "active": true
  },
  "affordances": {
    "next": "agc publishing endpoints"
  }
}

project profile resolved · dry-run on

Dry-run firstNothing is sent until you opt in.

Agent-readableJSON envelopes include next actions.

One surfaceCLI, local REST, and web share a registry.

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.

macOS Homebrew command

$ brew tap createitv/tap && brew install agc-cli && agc version

Windows Scoop command

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 version

Homebrew formula: agc-cli Versioned GitHub Release binary Winget PR submitted for Microsoft review

The 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

.agc/project.json project safe

{
  "appId": "123456789",
  "projectId": "987654321",
  "packageName": "com.example.app",
  "profile": "production"
}

No client keys or private keys are stored here.

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 / gameplay

Game Playing

registered

Outbound resource sync plus inbound AppGallery game playing callbacks.

DISCOVERagc gameplay endpoints --output table

STATUSagc gameplay status --pretty

LOCAL REST/api/v1/gameplay

8 typed interface entries

All endpoints 8

Expand an endpoint for registered parameters and commands. Consult its reference for full schemas, responses, and permissions.

POST查询资产明细asset-details{callbackUrl}

华为游戏服务器调用此接口查询玩家在玩游戏的资产明细数据，并将信息展示在游戏中心的“在玩”页面上。

Inbound callback to your service

Registered parameters
Parameter	Location	Required	Type	Description
`callbackUrl`	path	Yes	—	callbackUrl parameter
`callbackUrl`	path	Yes	—	callbackUrl parameter

Request body: json

Inspect definition

agc gameplay asset-details --pretty

Local REST definition

/api/v1/gameplay/endpoints/asset-details

Read endpoint reference ↗

POST查询资产概要asset-summary{callbackUrl}

华为游戏服务器调用此接口查询玩家在玩游戏的资产概要数据，并将信息展示在游戏中心的“在玩”页面上。

Inbound callback to your service

Registered parameters
Parameter	Location	Required	Type	Description
`callbackUrl`	path	Yes	—	callbackUrl parameter
`callbackUrl`	path	Yes	—	callbackUrl parameter

Request body: json

Inspect definition

agc gameplay asset-summary --pretty

Local REST definition

/api/v1/gameplay/endpoints/asset-summary

Read endpoint reference ↗

POST批量查询玩家基本信息basic-info{callbackUrl}

华为游戏服务器调用此接口批量查询玩家基本信息，并将信息展示在游戏中心的“在玩”页面上。

Inbound callback to your service

Registered parameters
Parameter	Location	Required	Type	Description
`callbackUrl`	path	Yes	—	callbackUrl parameter
`callbackUrl`	path	Yes	—	callbackUrl parameter

Request body: json

Inspect definition

agc gameplay basic-info --pretty

Local REST definition

/api/v1/gameplay/endpoints/basic-info

Read endpoint reference ↗

POST查询战绩筛选标签label{callbackUrl}

华为游戏服务器调用此接口查询玩家在玩游戏战绩的筛选标签，并将信息展示在游戏中心的“在玩”页面上。

Inbound callback to your service

Registered parameters
Parameter	Location	Required	Type	Description
`callbackUrl`	path	Yes	—	callbackUrl parameter
`callbackUrl`	path	Yes	—	callbackUrl parameter

Request body: json

Inspect definition

agc gameplay label --pretty

Local REST definition

/api/v1/gameplay/endpoints/label

Read endpoint reference ↗

POST上传/下架游戏资源resources/gameservice/api/gbClientApi

开发者服务器调用此接口同步华为服务器的游戏资源，用于上传或下架“在玩”页面上的图片或视频。

Developer-to-Huawei API

Registered parameters
Parameter	Location	Required	Type	Description

Parameters are not listed in the registry. See the reference.

Request body: json

Inspect definition

agc gameplay resources --pretty

Local REST definition

/api/v1/gameplay/endpoints/resources

Dry run (supply required parameters first)

agc gameplay resources --invoke --dry-run=true --body body.json

Read endpoint reference ↗

POST批量查询玩家角色信息role-info{callbackUrl}

华为游戏服务器调用此接口批量查询玩家角色信息。

Inbound callback to your service

Registered parameters
Parameter	Location	Required	Type	Description
`callbackUrl`	path	Yes	—	callbackUrl parameter
`callbackUrl`	path	Yes	—	callbackUrl parameter

Request body: json

Inspect definition

agc gameplay role-info --pretty

Local REST definition

/api/v1/gameplay/endpoints/role-info

Read endpoint reference ↗

POST分页查询玩家战绩scores{callbackUrl}

华为游戏服务器调用此接口分页查询玩家在玩游戏的战绩数据，并将信息展示在游戏中心的“在玩”页面上。

Inbound callback to your service

Registered parameters
Parameter	Location	Required	Type	Description
`callbackUrl`	path	Yes	—	callbackUrl parameter
`callbackUrl`	path	Yes	—	callbackUrl parameter

Request body: json

Inspect definition

agc gameplay scores --pretty

Local REST definition

/api/v1/gameplay/endpoints/scores

Read endpoint reference ↗

POST查询游戏概要信息summary{callbackUrl}

华为游戏服务器调用此接口查询玩家在玩游戏的概要数据，并将信息展示在游戏中心的“在玩”页面上。

Inbound callback to your service

Registered parameters
Parameter	Location	Required	Type	Description
`callbackUrl`	path	Yes	—	callbackUrl parameter
`callbackUrl`	path	Yes	—	callbackUrl parameter

Request body: json

Inspect definition

agc gameplay summary --pretty

Local REST definition

/api/v1/gameplay/endpoints/summary

Read 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: 2026-10-07

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 production

Bind 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 production

Inspect 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=false

Local 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

GET/api/v1/capabilitiesfamilies + affordances

GET/api/v1/endpointsall interface entries

GET/api/v1/openapi.jsonmachine-readable contract

POST/api/v1/:family/endpoints/:id/invokedry-run by default