Mini Game Management
Last updated: 2025-10-28 10:36:03
Mini games are a special type of mini program that can be played instantly without downloading, installing, or uninstalling.
From version 2.2.0, the Exclusive and Enterprise plans support the mini game features. You can develop, manage, and publish mini games using the Mini Program IDE and console.
Prerequisites
The mini game feature is currently available through an allowlist. Contact the product team to discuss your needs and enable it.
Mini game development guide
Mini game console operations
Create a mini game
Roles and permissions
Capability | Role | Super admin | Platform admin | Mini program administrator | Mini program senior developer | Mini program developer | Mini program operator | Mini program approver |
Mini game list | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Create, edit, submit/remove, delete mini game | Read-only | Read-only | ✓ | ✓ | - | - | - |
Super admin/Platform admin: Has read-only access to Mini game list module, and cannot create, edit, submit, remove, or delete mini games.
Mini program administrator/Mini program senior developer: Has access to Mini game list module, with permissions to create, edit, submit, remove, and delete mini games.
Mini program developer/Mini program operator/Mini program approver: Has viewing access to Mini game list module.
How to use
1. Navigate to Mini game management - Mini games, and click Create mini game.
2. Fill in the mini game information, including:
Mini game name: Required. It supports 3-64 characters including a-z, A-Z, 0-9, spaces and some special symbols ("+", "=", ",", ".", "@", "-", "_").
Mini game category: Required. Select an appropriate category for the mini game.
Mini game description: Required. Provide a description of the mini game, including gameplay, features, etc.
Mini game logo: Optional. Upload a square image in jpg or png format, up to 2 MB. If no logo is uploaded, the system default logo will be used.
Click Next. The mini game is now successfully created. If this is your first time creating a mini game, follow the instructions in step two to download and install the developer tools.
Development management
Development management includes setting domain names, applying for sensitive API permissions, querying real-time logs, and more.
Roles and permissions
Capability | Role | Super admin | Platform admin | Mini program administrator | Mini program senior developer | Mini program developer |
Domain settings | Read-only | Read-only | ✓ | ✓ | - |
API permission (sensitive API) request | Read-only | Read-only | ✓ | ✓ | - |
Real-time logs | Read-only | Read-only | ✓ | ✓ | ✓ |
Key management | Read-only | Read-only | ✓ | - | - |
Super admin/Platform admin: Has read-only access to Development management module.
Mini program administrator: Has access to Development management module, with permissions for domain settings, API access (sensitive API) requests, viewing real-time logs, and key management.
Mini program senior developer: Has access to Development management module, with permissions for domain settings, API access (sensitive API) requests, and viewing real-time logs.
Mini program developer: Has access to Development management module, with permission to view real-time logs.
Domain management
To ensure the security of superapp and its users, mini games are generally required to pre-configure their backend communication domains and may only communicate with specified domains.
Click Add domain name and enter the domain information, including regular HTTPS requests (wx.request), file uploads (wx.uploadFile), file downloads (wx.downloadFile), and WebSocket communication (wx.connectSocket). Embedding webpages in a mini game is supported (H5 page) to facilitate flexible configuration of the mini game.
If the mini game business is complex and domain names are difficult to configure comprehensively (e.g., dynamic ad request domains), the mini game can request to skip domain verification. After approval, domain settings are no longer required. Click Skip domain verification, fill in the reason for the application, read and agree to the security agreement, and submit the application.
API permissions
When the superapp that a mini game is linked to has enabled sensitive APIs, mini game developers must apply to the superapp for permission to use these sensitive APIs. The mini game can only access these APIs after approval from the superapp's administrator or approvers.
How to apply:
Request permissions: Apply for permission to use sensitive APIs from the superapp.
Real-time logs
Filters: Time, log level (All, Info and above, Warn and above, Error and above), system type, GUID, page link, filterMsg content, base library version, and client version.
Basic configurations
AppSecret
AppSecret (the mini game key) is essential for authentication in mini game login. Only mini game team administrators have the authority to view and manage the keys. They can generate, reset, and freeze keys in the key management section.
How to apply:
Generate
After clicking Generate, the mini game team admin needs to copy the key and securely save the key. Once the popup is closed, the key cannot be copied again. If the key is forgotten, it must be reset. Super App as a Service (SAS) does not display or save the key in plain text.
Reset
The mini game team admin can reset the key. After you confirm to reset the AppSecret, the mini game features using the original AppSecret cannot work properly, so please update it promptly.
Freeze
To ensure the mini game service's security, if the key is leaked or suspected to be leaked and has not yet been replaced, developers should freeze the key to prevent any security incidents.
The mini game team admin can click Freeze to freeze the key. After that, the mini game features using the original AppSecret will not work properly, so please update it promptly.
Openserver
Version management
Mini game version management provides lifecycle management for mini games.
Roles and permissions
Capability | Role | Super admin | Platform admin | Mini program administrator | Mini program senior developer | Mini program developer | Mini program operator | Mini program approver |
Upload mini game code/code packages | Read-only | Read-only | ✓ | ✓ | ✓ | - | - |
Submit approval request | Read-only | Read-only | ✓ | ✓ | - | - | ✓ |
Preview mini games | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ | ✓ |
Canary release | Read-only | Read-only | ✓ | ✓ | - | - | - |
Release version | Read-only | Read-only | ✓ | ✓ | - | - | ✓ |
Delete version | - | - | ✓ | ✓ | ✓ | - | - |
Super admin/Platform admin: Has read-only access to Version management module and cannot delete development versions.
Mini program administrator/Mini program senior developer: Has access to Version management module, with permissions to upload mini game code/code packages, submit approval request, preview mini games, perform canary releases, release versions of mini games, and delete development versions.
Mini program developer: Has access to Version management module, with permissions to upload mini game code/code packages, preview mini games, and delete development versions.
Mini program operator: Has access to Version management module, with permission to preview mini games.
Mini program approver: Has access to Version management module, with permissions to submit approval request, preview mini games, and release versions of mini games.
Version definition
Development version
After the developer submits the version of the mini game through the developer tool, a development version is generated in the Development version section on the Version management page. Click Submit for approval on the right to submit the mini game to the superapp for approval.
Version for approval
When a version is under approval, it is displayed in the section of Version approval progress. After it is approved, you can click Release to release the version.
Online version
The latest version of the mini game which has been released on the superapp is shown in this section. Click Download QR code on the right to save the mini game’s QR code to your device. You can then scan the QR code with the superapp to open the mini game.
Note
1. A developer can submit multiple development versions.
2. Different developers submitting development versions with the same version number will result in two versions with the same number under Version management - Development version.
3. The version number submitted for approval must be greater than the online version number and cannot use previously released version numbers.
4. After a version is released, the corresponding version number will be removed from the list of development versions.
Other features and operations
Mini game offline package
You can build a mini game into the superapp with the mini game offline package. Download the mini game package from the console, import it into the superapp project, and pack it together with the superapp. Users can open the embedded mini game without downloading it from the backend, even without an internet connection.
Directions
1. Download the mini game offline package.
2. Copy the downloaded mini game package to the custom assets directory. You need to strictly follow the naming rules for offline mini games.
Note:
Naming rules for offline mini games: {miniAppId}_{miniAppVersion}.apkg
3. In the SDK initialization configuration, specify the asset directory where the offline mini game was placed in the previous step.
Note
Offline mini games must go through the normal releasing process. Only the offline packages of online versions of mini games can be downloaded.
Offline mini games follow the same version management rules as online versions, including new releases, version rollbacks, and removal. If the online version differs from the pre-installed version, the client will fetch the online version.
If a mini game is removed, the corresponding offline mini game embedded in the superapp will also not be available.
Mini game version rollback
The online version of a mini game can be rolled back to a previously released version. However, continuous rollback is not supported.
Mini game removal
Click Remove to remove a mini game from the superapp. After that, the mini game can not be searched, and the cached mini game can not be opened.
Message subscription
Introduction
Message capabilities are essential for mini games. Superapp allows developers to send subscription messages, creating a closed-loop service. This lets developers quickly push business updates to users. To use this feature, go to the console, select Mini game management, and Message subscription. Then, pick suitable templates from the public library, configure the fields, and add them to My templates.
Roles and permissions
Capability | Role | Super admin | Platform admin | Mini program administrator | Mini program senior developer | Mini program developer |
My templates-view | Read-only | Read-only | ✓ | ✓ | ✓ |
My templates-delete | - | - | ✓ | ✓ | - |
Public template library-view | Read-only | Read-only | ✓ | ✓ | ✓ |
Public template library-select | - | - | ✓ | ✓ | - |
Super admin/Platform admin: Has read-only access to Message subscription module,with viewing permissions for My templates and Public template library.
Mini program administrator/Mini program senior developer: Has access to Message subscription module, with viewing and deletion permissions for My templates, and viewing and selection permissions for Public template library.
Mini program developer: Has access to Message subscription module, with viewing permissions for My templates and Public template library.
How to operate
Public template library
Developers can browse the public template library and select templates based on their business needs. Templates can also be searched by name.
Subscription types
One-time subscription
One-time subscription messages notify users about follow-up service steps after using the mini game.
When developers call the requestSubscribeMessage, a popup lets users opt-in to receive messages. Once subscribed, developers can send one service message at any time.
Note:
Long-term subscription is not supported in mini games.
Template selection
In the public template library, find the target template and click Select to enter the template configuration page. There are multiple keywords under each public template. Developers can select 1 to 5 keywords from the keyword list. Refer to the preview on the left for the pop-up content displayed to users on the superapp. Drag and drop the sorting button on the right side of the selected keywords to arrange their orders.
Click Submit to save the template to My templates.
Note:
If a same public template is added to My templates, the keywords in the template cannot be the same as those in the already added templates.
My templates
Templates selected and configured from the public template library will be added to My templates. Developers can use these templates to develop the message subscription feature.
Notes:
One-time template IDs and long-term template IDs cannot be used simultaneously.
Up to three messages can be subscribed to in a single call.
The subscription message page can only be triggered after the user has performed a click action.
In a single authorization call, each tmplId must correspond to a unique template title. If there are duplicates, only one will be retained.
Privacy policy
Configure the user privacy protection policy in the settings. Use the provided template to fill in the personal data collected by the mini game. After saving, the user privacy protection policy will be generated.
1. Click Update.
2. Fill in the privacy information.
Once saved, the user privacy protection policy can be viewed under More - Mini game details.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback