- Function Overview
- What's New
- Service Overview
- Getting Started
-
User Guide
- Configuration Management
- HTTP Proxy
- Commonly Used Commands
-
Options
- Option Overview
- Printing Help Information
- Printing Debugging Information
- Checking Command
- Specifying Region
- Calling APIs with an Account in Non-configuration Mode
- Calling APIs with AK/SK in Non-configuration Mode
- Calling APIs with a Token in Non-configuration Mode
- Calling APIs Using an Agency in Non-configuration Mode
- Specifying Account ID
- Specifying Profile
- Specifying Authentication Mode
- Specifying Output Format
- Passing API Parameters with JSON File
- Specifying Request Timeouts
- Specifying Retry Count
- Skipping HTTPS Request Certificate Verification
- Specifying a Domain Name
- Obtaining CLI Examples on API Explorer
- Using KooCLI in Non-configuration Mode
- Obtaining Authentication Information
-
FAQs
- Overview
- Authentication
- Profiles
- Metadata Cache
- Logs
- Network Connections
- Cloud Services
- Cloud Service APIs
- Regions
-
Parameters
- What Are KooCLI System Parameters?
- Why Am I Seeing a Message Indicating an Invalid Parameter?
- Why Are Old and New KooCLI System Parameters (Such as region and cli-region) Available? Which Parameters Are Recommended?
- Why Am I Seeing a Message Indicating a Duplicate Parameter?
- How Do I Use cli-jsonInput?
- When Can I Use cli-jsonInput?
- Why Am I Seeing a Message Indicating an Unsupported Parameter Position or Type?
- How Do I Leave a Body Parameter Empty for Cloud Service APIs?
- Interactive Mode and Autocomplete
-
Output Formats
- What Output Formats Are Supported by KooCLI?
- How Do I Define a JMESPath Expression?
- Which KooCLI System Parameters Are Related to Data Output? Which Ones Are Recommended?
- How Do I Use cli-output, cli-query, and cli-output-num?
- How Do I Use cli-output-rows, cli-output-cols, and cli-output-num? What Are the Precautions?
- How Do I Use cli-json-filter? What Are the Precautions?
- Other
- Videos
Show all
Function Overview
-
Profile Management
-
Profiles store common information required for calling cloud service APIs. They are defined by running KooCLI commands. All profiles constitute a configuration file, which is stored on your local host. When calling a cloud service API, you can specify a profile rather than manually inputting the common information.
KooCLI configuration commands are used to initialize configurations, and add, delete, modify, and query profiles.All regions
-
-
Autocomplete
-
After you turn on autocomplete for KooCLI, if you press Tab when entering a command, a prompt will appear to help you autocomplete the command.
All regions
-
-
Interactive Prompts
-
KooCLI provides powerful interactive prompts to facilitate command building on different platforms. Add --interactive in a command to enter the interactive mode. In this mode, the system displays cloud service names, API operations, parameters, and descriptions based on the information you enter. In addition, the system autocompletes the values of some parameters.
All regions
-
-
Metadata Management
-
KooCLI caches the metadata generated during API calling. You can manage the cached metadata files if necessary.
All regions
-
-
Version Query
-
You can query the KooCLI version you are using.
All regions
-
-
Version Upgrade
-
KooCLI supports automatic local upgrade. You can run a command to upgrade the current KooCLI to the latest version.
All regions
-
-
Log Management
-
KooCLI provides log recording and management to cache the logs generated during API calling.
All regions
-
-
Common Options
-
KooCLI options are system parameters that can be added to commands for calling APIs.
All regions
Viewing Help Information
Printing Debugging Information
Checking Command
Specifying Output Format
Specifying JSON File to Pass API Parameters
Specifying Request Timeout
Specifying Number of Connection Attempts
Skipping HTTPS Request Certificate Verification
Specifying a Domain Name
Using KooCLI in Non-configuration Mode
-
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.