Skip to main content

Documentation Index

Fetch the complete documentation index at: https://cobo.com/developers/llms.txt

Use this file to discover all available pages before exploring further.

Try Cobo WaaS Skill in your AI coding assistant (Claude Code, Cursor, etc.). Describe your needs in natural language to auto-generate production-ready SDK code and debug faster ๐Ÿš€
Cobo CLI provides several global options that can be used with any command to customize its behavior. These options allow you to control the environment, authentication method, and other settings for your CLI operations.
Global options should be placed before the specific command you want to run. For example, -e prod should come before get /wallets.

โ€‹
Available global options

โ€‹
Environment selection (-e, โ€”env)

The -e or --env option allows you to override the default environment for a specific command. 
cobo -e dev get /wallets
Possible values include:
  • dev: Development environment
  • prod: Production environment
If not specified, Cobo CLI will use the environment set in your configuration or default to the development environment.

โ€‹
Authentication method (-a, โ€”auth)

The -a or --auth option allows you to override the default authentication method for a specific command. 
cobo -a user get /wallets
Possible values include:
  • apikey: API key
  • user: Cobo Portal account
  • org: Org Access Token
If not specified, Cobo CLI will use the authentication method set in your configuration or default to API key authentication.

โ€‹
Debug mode (โ€”enable-debug)

The --enable-debug flag enables debug mode, which provides verbose logging for troubleshooting purposes. 
cobo --enable-debug get /wallets

โ€‹
Custom configuration file (โ€”config-file)

The --config-file option allows you to specify a custom configuration file instead of the default one. 
cobo --config-file /path/to/config.toml get /wallets
If not specified, Cobo CLI will use the default configuration file located in your home directory (~/.cobo/config.toml).

โ€‹
Custom API specification file (โ€”spec)

If you have a custom OpenAPI specification file, you can use it with Cobo CLI. This is useful for testing or working with different versions of the API. To use a custom specification file: 
$ cobo --spec /path/to/custom_spec.yaml get /wallets -d
Replace /path/to/custom_spec.yaml with the actual path to your custom specification file.
Using a custom specification file will override the default OpenAPI specification for that command only. It wonโ€™t affect other commands or future uses of Cobo CLI.

โ€‹
Combining global options

You can combine multiple global options in a single command: 
cobo -e prod -a user --enable-debug get /wallets
This command will:
  1. Use the production environment.
  2. Authenticate using your Cobo Portal account.
  3. Enable debug mode for verbose logging.
  4. Execute the GET request to retrieve wallet information.

โ€‹
Configuration precedence

The Cobo CLI follows the following order of precedence when determining which settings to use:
  1. Command line options (highest priority)
  2. Configuration file settings
  3. Default values (lowest priority)
This allows you to easily override settings on a per-command basis without modifying your configuration files.