Example usage
Here are some quick examples of how to use Cobo CLI:- List all Custodial Wallets:
- Use GraphQL to query Cobo WaaS:
- Create a new Cobo application using a template:
- Look up documentation for a specific API endpoint:
- Monitor real-time API requests:
- Trigger a webhook event:
- Listen for webhook events and forward them to a local endpoint:
Key features
- API interaction: Easily interact with Cobo WaaS 2.0 through RESTful and GraphQL based APIs directly from your terminal.
- API documentation lookup: Access helpful documentation for all Cobo WaaS APIs, requests, responses, and their parameters directly from the command line.
- Cobo Portal Applications: Build, manage, and publish Cobo Portal Applications, including creating apps from various application templates for different programming languages and frameworks.
- Real-time API monitoring: Stream API request logs for quick debugging and monitoring.
- Webhook testing: Test and debug your webhook integrations locally. (Coming soon)
- Multiple authentication methods: Utilize and test three types of authentication mechanisms: API keys, user access tokens, and org access tokens.
- Environment switching: Seamlessly switch between sandbox, development, and production environments for development and testing.
- Autocompletion: Enable autocompletion for faster command input and improved productivity.
Use cases
Cobo CLI is particularly useful for:- Developers integrating Cobo WaaS 2.0 into their applications
- DevOps engineers managing Cobo resources and monitoring transactions
- QA teams testing Cobo integrations and API responses
- Support teams troubleshooting customer issues related to Cobo services
Getting started
To begin using Cobo CLI, follow these steps:- Install Cobo CLI on your system.
- Log in and authenticate your Cobo account.
- Configure your environment for development or production use.
- Start exploring Cobo CLI commands to manage your wallets and transactions.
Cobo CLI is designed for use in test mode by default. Always exercise caution
when using it in a production environment, and ensure you understand the
implications of each command before execution.
