> ## 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. # List staking activities > This operation retrieves a list of staking activities. Try [Cobo WaaS Skill](/v2/guides/overview/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 🚀 ```python Python theme={null} import cobo_waas2 from cobo_waas2.models.activity_status import ActivityStatus from cobo_waas2.models.activity_type import ActivityType from cobo_waas2.models.list_staking_activities200_response import ( ListStakingActivities200Response, ) from cobo_waas2.rest import ApiException from pprint import pprint # See configuration.py for a list of all supported configurations. configuration = cobo_waas2.Configuration( # Replace `` with your private key api_private_key="", # Select the development environment. To use the production environment, change the URL to https://api.cobo.com/v2. host="https://api.dev.cobo.com/v2", ) # Enter a context with an instance of the API client with cobo_waas2.ApiClient(configuration) as api_client: # Create an instance of the API class api_instance = cobo_waas2.StakingsApi(api_client) pool_id = "babylon_btc" staking_id = "f47ac10b-58cc-4372-a567-0e02b2c3d479" activity_type = cobo_waas2.ActivityType() activity_status = cobo_waas2.ActivityStatus() min_modified_timestamp = 1635744000000 max_modified_timestamp = 1635744000000 initiator = "steve@example.com" request_id = "web_send_by_user_327_1610444045047" limit = 10 before = "RqeEoTkgKG5rpzqYzg2Hd3szmPoj2cE7w5jWwShz3C1vyGmk1" after = "RqeEoTkgKG5rpzqYzg2Hd3szmPoj2cE7w5jWwShz3C1vyGSAk" try: # List staking activities api_response = api_instance.list_staking_activities( pool_id=pool_id, staking_id=staking_id, activity_type=activity_type, activity_status=activity_status, min_modified_timestamp=min_modified_timestamp, max_modified_timestamp=max_modified_timestamp, initiator=initiator, request_id=request_id, limit=limit, before=before, after=after, ) print("The response of StakingsApi->list_staking_activities:\n") pprint(api_response) except Exception as e: print("Exception when calling StakingsApi->list_staking_activities: %s\n" % e) ``` ```java Java theme={null} // Import classes: import com.cobo.waas2.ApiClient; import com.cobo.waas2.ApiException; import com.cobo.waas2.Configuration; import com.cobo.waas2.Env; import com.cobo.waas2.api.StakingsApi; import com.cobo.waas2.model.*; public class Example { public static void main(String[] args) { ApiClient defaultClient = Configuration.getDefaultApiClient(); // Select the development environment. To use the production environment, replace `Env.DEV` with // `Env.PROD defaultClient.setEnv(Env.DEV); // Replace `` with your private key defaultClient.setPrivKey(""); StakingsApi apiInstance = new StakingsApi(); String poolId = "babylon_btc"; String stakingId = "f47ac10b-58cc-4372-a567-0e02b2c3d479"; ActivityType activityType = ActivityType.fromValue("Stake"); ActivityStatus activityStatus = ActivityStatus.fromValue("Success"); Long minModifiedTimestamp = 1635744000000L; Long maxModifiedTimestamp = 1635744000000L; String initiator = "steve@example.com"; String requestId = "web_send_by_user_327_1610444045047"; Integer limit = 10; String before = "RqeEoTkgKG5rpzqYzg2Hd3szmPoj2cE7w5jWwShz3C1vyGmk1"; String after = "RqeEoTkgKG5rpzqYzg2Hd3szmPoj2cE7w5jWwShz3C1vyGSAk"; try { ListStakingActivities200Response result = apiInstance.listStakingActivities( poolId, stakingId, activityType, activityStatus, minModifiedTimestamp, maxModifiedTimestamp, initiator, requestId, limit, before, after); System.out.println(result); } catch (ApiException e) { System.err.println("Exception when calling StakingsApi#listStakingActivities"); System.err.println("Status code: " + e.getCode()); System.err.println("Reason: " + e.getResponseBody()); System.err.println("Response headers: " + e.getResponseHeaders()); e.printStackTrace(); } } } ``` ```go Go theme={null} package main import ( "context" "fmt" coboWaas2 "github.com/CoboGlobal/cobo-waas2-go-sdk/cobo_waas2" "github.com/CoboGlobal/cobo-waas2-go-sdk/cobo_waas2/crypto" "os" ) func main() { poolId := "babylon_btc" stakingId := "f47ac10b-58cc-4372-a567-0e02b2c3d479" activityType := coboWaas2.ActivityType("Stake") activityStatus := coboWaas2.ActivityStatus("Success") minModifiedTimestamp := int64(1635744000000) maxModifiedTimestamp := int64(1635744000000) initiator := "steve@example.com" requestId := "web_send_by_user_327_1610444045047" limit := int32(10) before := "RqeEoTkgKG5rpzqYzg2Hd3szmPoj2cE7w5jWwShz3C1vyGmk1" after := "RqeEoTkgKG5rpzqYzg2Hd3szmPoj2cE7w5jWwShz3C1vyGSAk" configuration := coboWaas2.NewConfiguration() // Initialize the API client apiClient := coboWaas2.NewAPIClient(configuration) ctx := context.Background() // Select the development environment. To use the production environment, replace coboWaas2.DevEnv with coboWaas2.ProdEnv ctx = context.WithValue(ctx, coboWaas2.ContextEnv, coboWaas2.DevEnv) // Replace `` with your private key ctx = context.WithValue(ctx, coboWaas2.ContextPortalSigner, crypto.Ed25519Signer{ Secret: "", }) resp, r, err := apiClient.StakingsAPI.ListStakingActivities(ctx). PoolId(poolId). StakingId(stakingId). ActivityType(activityType). ActivityStatus(activityStatus). MinModifiedTimestamp(minModifiedTimestamp). MaxModifiedTimestamp(maxModifiedTimestamp). Initiator(initiator). RequestId(requestId). Limit(limit). Before(before). After(after). Execute() if err != nil { fmt.Fprintf(os.Stderr, "Error when calling `StakingsAPI.ListStakingActivities``: %v\n", err) fmt.Fprintf(os.Stderr, "Full HTTP response: %v\n", r) } // response from `ListStakingActivities`: ListStakingActivities200Response fmt.Fprintf(os.Stdout, "Response from `StakingsAPI.ListStakingActivities`: %v\n", resp) } ``` ```javascript JavaScript theme={null} const CoboWaas2 = require("@cobo/cobo-waas2"); // Initialize the API client const apiClient = CoboWaas2.ApiClient.instance; // Select the development environment. To use the production environment, replace `Env.DEV` with `Env.PROD` apiClient.setEnv(CoboWaas2.Env.DEV); // Replace `` with your private key apiClient.setPrivateKey(""); // Call the API const apiInstance = new CoboWaas2.StakingsApi(); const opts = { pool_id: "babylon_btc", staking_id: "f47ac10b-58cc-4372-a567-0e02b2c3d479", activity_type: new CoboWaas2.ActivityType(), activity_status: new CoboWaas2.ActivityStatus(), min_modified_timestamp: 1635744000000, max_modified_timestamp: 1635744000000, initiator: "steve@example.com", request_id: "web_send_by_user_327_1610444045047", limit: 10, before: "RqeEoTkgKG5rpzqYzg2Hd3szmPoj2cE7w5jWwShz3C1vyGmk1", after: "RqeEoTkgKG5rpzqYzg2Hd3szmPoj2cE7w5jWwShz3C1vyGSAk", }; apiInstance.listStakingActivities(opts).then( (data) => { console.log("API called successfully. Returned data: " + data); }, (error) => { console.error(error); }, ); ``` ## OpenAPI ````yaml get /stakings/activities openapi: 3.0.3 info: title: Cobo Wallet as a Service 2.0 description: > The Cobo Wallet-as-a-Service (WaaS) 2.0 API is the latest version of Cobo's WaaS API offering. It enables you to access Cobo's full suite of crypto wallet technologies with powerful and flexible access controls. By encapsulating complex security protocols and streamlining blockchain interactions, this API allows you to concentrate on your core business activities without worrying about the safety of your assets. The WaaS 2.0 API presents the following key features: - A unified API for Cobo's [all four wallet types](https://manuals.cobo.com/en/portal/introduction#an-all-in-one-wallet-platform) - Support for 80+ chains and 3000+ tokens - A comprehensive selection of webhook events - Flexible usage models for MPC Wallets, including [Organization-Controlled Wallets](https://manuals.cobo.com/en/portal/mpc-wallets/ocw/introduction) and [User-Controlled Wallets](https://manuals.cobo.com/en/portal/mpc-wallets/ucw/introduction) - Programmatic control of smart contract wallets such as Safe{Wallet} with fine-grained access controls - Seamlessly transfer funds across multiple exchanges, including Binance, OKX, Bybit, Deribit, and more For more information about the WaaS 2.0 API, see [Introduction to WaaS 2.0](https://www.cobo.com/developers/v2/guides/overview/introduction). termsOfService: https://cobo.com/waas/tos/ license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html contact: name: Cobo WaaS url: https://www.cobo.com/waas email: help@cobo.com version: 1.0.0 servers: - url: https://api.dev.cobo.com/v2 description: Development environment - url: https://api.cobo.com/v2 description: Production environment security: - CoboAuth: [] tags: - name: Organizations description: Operations related to Organizations. - name: Wallets description: Operations related to all wallets. - name: Wallets - MPC Wallets description: Operations related to mpc wallet. - name: Wallets - Exchange Wallet description: Operations related to exchange wallet. - name: Wallets - Smart Contract Wallets description: Operations related to smart contract wallet. - name: Transactions description: Operations related to all transactions. - name: Developers - Webhooks description: Operations related to webhooks. - name: Stakings description: Operations related to staking. - name: OAuth description: Operations related to OAuth. - name: Developers description: Operations related to developers. - name: AddressBooks description: Operations related to address books. - name: TravelRule description: Operations related to travel rule. - name: GraphQL description: Operations related to executing GraphQL queries and mutations. - name: PrimeBroker description: Operations related to prime broker. - name: AppWorkflows description: Operations related to app workflow. - name: FeeStation description: Operations related to fee station. - name: Payment description: Operations related to payment. - name: Batch Payouts description: Operations related to batch payouts. - name: Tokenization description: Operations related to tokenization. - name: AutoSweep description: Operations related to auto sweep. - name: Compliance description: Operations related to compliance. paths: /stakings/activities: get: tags: - Stakings summary: List staking activities description: | This operation retrieves a list of staking activities. operationId: list_staking_activities parameters: - $ref: '#/components/parameters/poolIdOptionalParam' - $ref: '#/components/parameters/stakingIdOptionalParam' - $ref: '#/components/parameters/activityTypeOptionalParam' - $ref: '#/components/parameters/activityStatusOptionalParam' - $ref: '#/components/parameters/minModifiedTimestampOptionalParam' - $ref: '#/components/parameters/maxModifiedTimestampOptionalParam' - $ref: '#/components/parameters/activityInitiatorOptionalParam' - $ref: '#/components/parameters/optionalRequestIdParam' - $ref: '#/components/parameters/limitParam' - $ref: '#/components/parameters/beforeParam' - $ref: '#/components/parameters/afterParam' responses: '200': $ref: '#/components/responses/listActivitiesResponse' 4XX: $ref: '#/components/responses/badRequestError' 5XX: $ref: '#/components/responses/internalServerError' security: - CoboAuth: [] - OAuth2: - wallet.read components: parameters: poolIdOptionalParam: name: pool_id in: query required: false description: >- The ID of the staking pool. A staking pool is a pairing of a staking protocol and a specific type of token. You can call [List staking pools](https://www.cobo.com/developers/v2/api-references/stakings/list-staking-pools) to retrieve a list of staking pools. schema: type: string example: babylon_btc stakingIdOptionalParam: name: staking_id in: query required: false description: The ID of the Phase-1 BTC staking position. schema: type: string example: f47ac10b-58cc-4372-a567-0e02b2c3d479 activityTypeOptionalParam: name: activity_type in: query required: false schema: $ref: '#/components/schemas/ActivityType' example: Stake activityStatusOptionalParam: name: activity_status in: query required: false schema: $ref: '#/components/schemas/ActivityStatus' example: Success minModifiedTimestampOptionalParam: name: min_modified_timestamp in: query required: false description: >- The start time of the query. All staking activities updated after the specified time will be retrieved. The time is in Unix timestamp format, measured in milliseconds. schema: type: integer format: int64 example: 1635744000000 maxModifiedTimestampOptionalParam: name: max_modified_timestamp in: query required: false description: >- The end time of the query. All staking activities updated before the specified time will be retrieved. The time is in Unix timestamp format, measured in milliseconds. schema: type: integer format: int64 example: 1635744000000 activityInitiatorOptionalParam: name: initiator in: query required: false description: >- The activity initiator, which is your API key by default. You can also specify the initiator when creating the activity. schema: type: string example: steve@example.com optionalRequestIdParam: name: request_id in: query required: false description: >- The request ID that is used to track a transaction request. The request ID is provided by you and must be unique within your organization. schema: type: string example: web_send_by_user_327_1610444045047 limitParam: name: limit in: query description: >- The maximum number of objects to return. For most operations, the value range is [1, 50]. required: false schema: type: integer format: int32 default: 10 example: 10 beforeParam: name: before in: query description: > A cursor indicating the position before the current page. This value is generated by Cobo and returned in the response. If you are paginating forward from the beginning, you do not need to provide it on the first request. When paginating backward (to the previous page), you should pass the before value returned from the last response. required: false schema: type: string example: RqeEoTkgKG5rpzqYzg2Hd3szmPoj2cE7w5jWwShz3C1vyGmk1 afterParam: name: after in: query description: > A cursor indicating the position after the current page. This value is generated by Cobo and returned in the response. You do not need to provide it on the first request. When paginating forward (to the next page), you should pass the after value returned from the last response. required: false schema: type: string example: RqeEoTkgKG5rpzqYzg2Hd3szmPoj2cE7w5jWwShz3C1vyGSAk responses: listActivitiesResponse: description: A list of staking activities have been successfully retrieved. content: application/json: schema: type: object properties: data: items: $ref: '#/components/schemas/Activity' type: array pagination: $ref: '#/components/schemas/Pagination' badRequestError: description: >- Bad request. Your request contains malformed syntax or invalid parameters. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' internalServerError: description: Internal server error. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' schemas: ActivityType: type: string enum: - Stake - Unstake - Withdraw - Claim example: Stake description: > The type of the staking activity. Possible values include: - `Stake`: Stake tokens. - `Unstake`: Unstake tokens. Unstaked tokens are still in the staking protocol. - `Withdraw`: Withdraw tokens from the staking protocol to your wallet. - `Claim`: Claim rewards from the staking protocol. ActivityStatus: type: string enum: - Success - Processing - Failed example: Success description: | The status of the staking activity. Possible values include: - `Success`: The activity is successfully completed. - `Processing`: The activity is being processed. - `Failed`: The activity has failed. Activity: type: object description: The staking activity. required: - stake_id - pool_id - amount - status - created_at - updated_at - token_id properties: id: description: The activity ID. type: string example: 0011039d-27fb-49ba-b172-6e0aa80e37ec initiator: description: The initiator of the activity. type: string example: steve@example.com initiator_type: $ref: '#/components/schemas/TransactionInitiatorType' type: $ref: '#/components/schemas/ActivityType' wallet_id: type: string example: 0111039d-27fb-49ba-b172-6e0aa80e37ec description: The staker's wallet ID. address: type: string example: '0xAbCdE123456789aBcDeF123456789aBcDeF12345' description: The staker's wallet address. pool_id: $ref: '#/components/schemas/StakingPoolId' token_id: type: string example: BTC description: The token ID. staking_id: type: string example: 0011039d-27fb-49ba-b172-6e0aa80e37ec description: The ID of the corresponding staking position. request_ids: type: array items: type: string example: f47ac10b-58cc-4372-a567-0e02b2c3d479 description: The request IDs of the corresponding transactions of the activity. amount: type: string example: '100.00' description: The staking amount. transaction_ids: type: array items: type: string example: 0011039d-27fb-49ba-b172-6e0aa80e37ec description: The IDs of the corresponding transactions of the activity. timeline: type: array items: $ref: '#/components/schemas/ActivityTimeline' description: The timeline of the activity. fee: $ref: '#/components/schemas/TransactionRequestFee' status: $ref: '#/components/schemas/ActivityStatus' extra: oneOf: - $ref: '#/components/schemas/BabylonStakingActivityDetailExtra' - $ref: '#/components/schemas/EthStakingActivityDetailExtra' - $ref: '#/components/schemas/CoreStakingActivityDetailExtra' discriminator: propertyName: pool_type mapping: Babylon: $ref: '#/components/schemas/BabylonStakingActivityDetailExtra' ETHBeacon: $ref: '#/components/schemas/EthStakingActivityDetailExtra' CoreBTC: $ref: '#/components/schemas/CoreStakingActivityDetailExtra' created_timestamp: description: The time when the activity was created. type: integer format: int64 example: 1640995200000 updated_timestamp: description: The time when the activity was last updated. type: integer format: int64 example: 1640995200000 Pagination: type: object description: The pagination information of the returned data. required: - before - after - total_count properties: before: type: string example: RqeEoTkgKG5rpzqYzg2Hd3szmPoj2cE7w5jWwShz3C1vyGmk1 description: > An object ID used to retrieve records before the specified object, indicating earlier or smaller records relative to the current dataset. You can use it to paginate backwards. If empty, it means you have reached the start of the data. Most API endpoints sort by object ID, but some use other fields depending on the endpoint. after: type: string example: RqeEoTkgKG5rpzqYzg2Hd3szmPoj2cE7w5jWwShz3C1vyGSAk description: > An object ID used to retrieve records after the specified object, indicating newer or larger records relative to the current dataset. You can use it to paginate forwards. If empty, it means you have reached the end of the data. Most API endpoints sort by object ID, but some use other fields depending on the endpoint. total_count: type: integer example: 10000 description: >- The total number of records that match the query criteria, unaffected by the pagination parameters (`before` , `after`, and `limit`). ErrorResponse: type: object description: The response of a failed request. required: - error_code - error_message - error_id properties: error_code: type: integer description: >- The error code. Refer to [Error codes and status codes](https://www.cobo.com/developers/v2/api-references/error-codes) for more details. error_message: type: string description: The error description. error_id: type: string description: >- The error log ID. You can provide the error ID when submitting a ticket to help Cobo to locate the issue. example: 0b6ddf19083c4bd1a9ca01bec44b24dd TransactionInitiatorType: type: string enum: - API - Web - App - External example: API description: | The transaction initiator type. Possible values include: - `API`: An API initiator, who initiates the transaction by using the WaaS API. - `Web`: An web initiator, who initiates the transaction from Cobo Portal. - `App`: An App initiator, who initiates the transaction from Cobo Portal Apps. - `External`: An external initiator, who initiates the transaction outside Cobo. StakingPoolId: type: string enum: - babylon_btc_signet - babylon_btc - beacon_eth - beacon_eth_holesky - core_btc - core_xtn - sky_farm_eth_usdc - bithive_signet - bithive - beacon_bera - beacon_bera_testnet - berachain_bgt - berachain_bgt_testnet example: babylon_btc_signet description: >- The ID of the staking pool. A staking pool is a pairing of a staking protocol and a specific type of token. Currently, `berachain_bgt` and `berachain_bgt_testnet` are not supported. ActivityTimeline: description: The timeline of the staking activity. type: object required: - action properties: action: $ref: '#/components/schemas/ActivityAction' status: type: string example: success description: | The status of the action. Possible values include: - `Success`: The action is successfully completed. - `Processing`: The action is being processed. - `Failed`: The action has failed. timestamp: type: integer format: int64 example: 1640995200000 description: > The time when the action took place, in Unix timestamp format, measured in milliseconds. - For the `Submitted` action, `timestamp` represents the time the staking, unstaking, or withdrawal request was created. - For the `BTCConfirmation` action, `timestamp` represents the time when the request was confirmed on the Bitcoin chain, or when the confirmation failed. - For the `BabylonConfirmation` action, `timestamp` represents the time when the request was confirmed by the Babylon protocol, or when the confirmation failed. transaction_id: type: string description: The ID of the corresponding transaction. example: aff0e1cb-15b2-4e1f-9b9d-a9133715986f TransactionRequestFee: oneOf: - $ref: '#/components/schemas/TransactionRequestFixedFee' - $ref: '#/components/schemas/TransactionRequestEvmEip1559Fee' - $ref: '#/components/schemas/TransactionRequestEvmLegacyFee' - $ref: '#/components/schemas/TransactionRequestUtxoFee' - $ref: '#/components/schemas/TransactionRequestSOLFee' - $ref: '#/components/schemas/TransactionRequestFILFee' discriminator: propertyName: fee_type mapping: Fixed: $ref: '#/components/schemas/TransactionRequestFixedFee' EVM_EIP_1559: $ref: '#/components/schemas/TransactionRequestEvmEip1559Fee' EVM_Legacy: $ref: '#/components/schemas/TransactionRequestEvmLegacyFee' UTXO: $ref: '#/components/schemas/TransactionRequestUtxoFee' SOL: $ref: '#/components/schemas/TransactionRequestSOLFee' FIL: $ref: '#/components/schemas/TransactionRequestFILFee' BabylonStakingActivityDetailExtra: title: Babylon allOf: - $ref: '#/components/schemas/BaseStakeExtra' - type: object description: The staking information specific to the Babylon protocol. properties: finality_provider_public_key: description: The public key of the finality provider. type: string pattern: ^[0-9a-fA-F]{64}$ example: eca1b104dce16c30705f4147a9c4a373ac88646c5d1bcda6a89c018940cb96a0 stake_block_time: description: >- The number of blocks that need to be processed before the locked tokens are unlocked and become accessible. type: integer format: int64 example: 2000 auto_broadcast: description: > Whether to automatically broadcast the transaction. - `true`: Automatically broadcast the transaction. - `false`: The transaction will not be submitted to the blockchain automatically. You can call [Broadcast signed transactions](https://www.cobo.com/developers/v2/api-references/transactions/broadcast-signed-transactions) to broadcast the transaction to the blockchain, or retrieve the signed raw transaction data `raw_tx` by calling [Get transaction information](https://www.cobo.com/developers/v2/api-references/transactions/get-transaction-information) and broadcast it yourself. type: boolean example: false EthStakingActivityDetailExtra: title: Ethereum Beacon Chain allOf: - $ref: '#/components/schemas/BaseStakeExtra' - type: object description: The staking information specific to the Ethereum Beacon Chain. properties: provider_name: description: The name of the provider. type: string example: Stakefish validator_pubkeys: description: >- A list of public keys associated with the Ethereum validators for this unstaking operation. type: array items: type: string example: - '0x1234567890987654321012345678909876543210' - '0x1234567890987654321012345678909876543210' CoreStakingActivityDetailExtra: title: CoreBTC allOf: - $ref: '#/components/schemas/BaseStakeExtra' - type: object description: The staking information specific to the CORE staking protocol. properties: timelock: description: >- The Unix timestamp (in seconds) when the staking position will be unlocked and available for withdrawal. type: integer example: 1704067200 change_address: description: >- The change address on the Bitcoin chain. If not provided, the source wallet's address will be used as the change address. type: string example: bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh validator_address: description: The validator's EVM address. type: string example: '0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045' reward_address: description: The EVM address to receive staking rewards. type: string example: '0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045' ActivityAction: type: string enum: - Submitted - BTCConfirmation - BabylonConfirmation - DepositETH - ClaimRewards - ActivateValidator - UnstakeETH - ApproveUSDC - ConvertToUSDS - ApproveUSDS - DepositUSDS - WithdrawUSDS - ConvertToUSDC example: Submitted description: | The specific action taken within an activity. Possible values include: - `Submitted`: Submit the staking, unstaking, or withdrawal request. - `BTCConfirmation`: The Bitcoin chain confirms the request. - `BabylonConfirmation`: The Babylon protocol confirms the request. - `DepositETH`: Deposit ETH to the validator to start staking. - `ClaimRewards`: Claim the rewards from the validator. - `ActivateValidator`: Activate the validator to start staking. - `UnstakeETH`: Unstake ETH from the validator. - `ApproveUSDC`: Grant permission for the protocol to use your USDC. - `ConvertToUSDS`: Convert your USDC to USDS. - `ApproveUSDS`: Grant permission for the protocol to use your USDS. - `DepositUSDS`: Stake the USDS with the validator. - `WithdrawUSDS`: Withdraw the USDS from the protocol. - `ConvertToUSDC`: Convert USDS back to USDC. TransactionRequestFixedFee: type: object description: > The preset properties to limit transaction fee. In the fixed fee model, the transaction fee is a fixed amount within a certain amount of period regardless of the transaction size or network congestion, which can vary between different chains. For more information about the fixed fee model, refer to [Fee models](https://www.cobo.com/developers/v2/guides/transactions/estimate-fees#fee-models). You can specify the maximum fee amount to limit the transaction fee. The transaction will fail if the transaction fee exceeds the specified maximum fee amount. Switch between the tabs to display the properties for different transaction fee models. title: Fixed required: - fee_type - token_id allOf: - type: object properties: fee_type: $ref: '#/components/schemas/FeeType' token_id: type: string description: The token used to pay the transaction fee. example: TRON - $ref: '#/components/schemas/MaxFeeAmount' TransactionRequestEvmEip1559Fee: type: object description: > The preset properties to limit transaction fee. For more information about the EIP-1559 fee model, refer to [Fee models](https://www.cobo.com/developers/v2/guides/transactions/estimate-fees#fee-models). You can specify the maximum gas fee per gas unit, maximum priority fee per gas unit, and the gas limit to limit the gas price, priority fee per gas unit, gas units used in the transaction. Switch between the tabs to display the properties for different transaction fee models. title: EVM_EIP_1559 required: - fee_type - token_id - max_fee_per_gas - max_priority_fee_per_gas allOf: - type: object properties: fee_type: $ref: '#/components/schemas/FeeType' token_id: type: string description: The token used to pay the transaction fee. example: ETH gas_limit: type: string description: >- The gas limit. It represents the maximum number of gas units that you are willing to pay for the execution of a transaction or Ethereum Virtual Machine (EVM) operation. The gas unit cost of each operation varies. example: '21000' - $ref: '#/components/schemas/EvmEip1559FeeBasePrice' TransactionRequestEvmLegacyFee: type: object description: > The preset properties to limit transaction fee. For more information about the Legacy fee model, refer to [Fee models](https://www.cobo.com/developers/v2/guides/transactions/estimate-fees#fee-models). You can specify the gas limit to limit the gas units used in the transaction. Switch between the tabs to display the properties for different transaction fee models. required: - fee_type - token_id - gas_price title: EVM_Legacy allOf: - type: object properties: fee_type: $ref: '#/components/schemas/FeeType' token_id: type: string description: The token used to pay the transaction fee. example: ETH gas_limit: type: string description: >- The gas limit. It represents the maximum number of gas units that you are willing to pay for the execution of a transaction or Ethereum Virtual Machine (EVM) operation. The gas unit cost of each operation varies. example: '21000' - $ref: '#/components/schemas/EvmLegacyFeeBasePrice' TransactionRequestUtxoFee: type: object description: > The preset properties to limit transaction fee. For more information about the UTXO fee model, see [Fee models](https://www.cobo.com/developers/v2/guides/transactions/estimate-fees#fee-models). You can specify the maximum fee amount to limit the transaction fee. The transaction will fail if the transaction fee exceeds the specified maximum fee amount. Switch between the tabs to display the properties for different transaction fee models. required: - fee_type - token_id title: UTXO allOf: - type: object properties: fee_type: $ref: '#/components/schemas/FeeType' token_id: type: string description: The token used to pay the transaction fee. example: BTC max_fee_amount: type: string description: >- The maximum fee that you are willing to pay for the transaction. Provide the value without applying precision. The transaction will fail if the transaction fee exceeds the maximum fee. example: '0.1' - $ref: '#/components/schemas/UtxoFeeBasePrice' TransactionRequestSOLFee: type: object description: > The preset properties to limit transaction fee. For more information about the SOL fee model, see [Fee models](https://www.cobo.com/developers/v2/guides/transactions/estimate-fees#fee-models). You can specify CU price and CU limit to adjust the priority and resource allocation of your transaction. Switch between the tabs to display the properties for different transaction fee models. title: SOL required: - fee_type - token_id - compute_unit_price - compute_unit_limit allOf: - type: object properties: fee_type: $ref: '#/components/schemas/FeeType' token_id: type: string description: The token used to pay the transaction fee. example: ETH - $ref: '#/components/schemas/SOLComputeUnit' TransactionRequestFILFee: type: object description: > The preset properties to limit transaction fee. For more information about the FIL fee model, see [Fee models](https://www.cobo.com/developers/v2/guides/transactions/estimate-fees#fee-models). You can specify the gas fee cap, gas premium, and gas limit to control fee behavior and prioritization. Switch between the tabs to display the properties for different transaction fee models. title: FIL required: - fee_type - token_id - gas_fee_cap - gas_premium allOf: - type: object properties: fee_type: $ref: '#/components/schemas/FeeType' token_id: type: string description: The token used to pay the transaction fee. example: ETH - $ref: '#/components/schemas/FILPrice' BaseStakeExtra: type: object description: The base information about a staking protocol. required: - pool_type properties: pool_type: $ref: '#/components/schemas/StakingPoolType' FeeType: type: string enum: - Fixed - EVM_EIP_1559 - EVM_Legacy - UTXO - SOL - FIL example: EVM_EIP_1559 default: EVM_EIP_1559 description: > The fee model. Possible values include: - `Fixed`: The fixed fee model. - `EVM_EIP_1559`: The EIP-1559 fee model. - `EVM_Legacy`: The legacy fee model. - `UTXO`: The fee model used in UTXO-based blockchains, such as Bitcoin. - `SOL`: The fee model used in Solana. - `FIL`: The fee model used in Filecoin. Each fee model requires a different set of properties. Switch between the above tabs for details. To learn more about the fee models, refer to [Fee models](https://www.cobo.com/developers/v2/guides/transactions/estimate-fees#fee-models). MaxFeeAmount: type: object properties: max_fee_amount: type: string description: >- The maximum fee that you are willing to pay for the transaction. Provide the value without applying precision. The transaction will fail if the transaction fee exceeds the maximum fee. example: '0.1' EvmEip1559FeeBasePrice: type: object properties: max_fee_per_gas: type: string description: The maximum gas fee per gas unit used on the chain, in wei. example: '9000000000000' max_priority_fee_per_gas: type: string description: >- The maximum priority fee per gas unit used, in wei. The maximum priority fee represents the highest amount of miner tips that you are willing to pay for your transaction. example: '1000000000000' EvmLegacyFeeBasePrice: type: object properties: gas_price: type: string description: >- The gas price, in wei. The gas price represents the amount of ETH that must be paid to validators for processing transactions per gas unit used. example: '100000000' UtxoFeeBasePrice: type: object properties: fee_rate: type: string description: >- The fee rate in sat/vByte. The fee rate represents the satoshis you are willing to pay for each byte of data that your transaction will consume on the blockchain. example: '50' SOLComputeUnit: type: object properties: compute_unit_price: type: string description: >- The price paid per compute unit. This value determines the priority fee for the transaction, allowing you to increase inclusion probability in congested conditions. example: '0.0001' compute_unit_limit: type: string description: >- The maximum number of compute units your transaction is allowed to consume. It sets an upper bound on computational resource usage to prevent overload. example: '200000' FILPrice: type: object properties: gas_premium: type: string description: >- An optional tip you can include to prioritize your transaction. The gas premium incentivizes miners to include your transaction sooner than those offering only the base fee. example: '0.0001' gas_fee_cap: type: string description: The maximum gas price you are willing to pay per unit of gas. example: '0.00035' gas_limit: type: string description: The maximum amount of gas your transaction is allowed to consume. example: '500' StakingPoolType: type: string enum: - Babylon - ETHBeacon - CoreBTC - SkyFarm - BitHive - BERABeacon - BeraChainBGT example: Babylon description: | The type of the staking pool. Possible values are: - `Babylon`: Babylon staking pool - `ETHBeacon`: Ethereum Beacon Chain staking pool - `CoreBTC`: Core BTC staking pool - `SkyFarm`: SKY farm staking pool - `BitHive`: BitHive staking pool - `BERABeacon`: BERA Beacon Chain staking pool - `BeraChainBGT`: Bera Chain BGT staking pool securitySchemes: CoboAuth: type: apiKey in: header name: BIZ-API-KEY description: > The API key. For more details, refer to [API key](https://www.cobo.com/developers/v2/guides/overview/cobo-auth#api-key). In the API playground, enter your [API secret](https://www.cobo.com/developers/v2/guides/overview/cobo-auth#api-secret), and your API key will be accordingly calculated. OAuth2: type: oauth2 description: >- The [Org Access Token](https://www.cobo.com/developers/v2/apps/org-access-tokens). Use this authorization method only if you are developing Cobo Portal Apps for installation and use across different organizations. flows: authorizationCode: authorizationUrl: https://auth.cobo.com/authorize tokenUrl: https://auth.cobo.com/oauth/token scopes: address_book.read: Read address book api_key.read: Read API key information callback.read: Read callback message callback.resend: Resend callback message wallet.create: Create wallet wallet.read: Read wallet information wallet.update: Update wallet information wallet.delete: Delete wallet information wallet.create_address: Create wallet address wallet.manage_utxo: Manage UTXO mpc_project.create: Create MPC project mpc_project.read: Read MPC project information mpc_project.update: Update MPC project information mpc_vault.create: Create MPC Vault mpc_vault.read: Read MPC Vault information mpc_vault.update: Update MPC Vault information mpc_key_group.create: Create MPC key group mpc_key_group.read: Read MPC key group information mpc_key_group.update: Update MPC key group information mpc_key_group.delete: Delete MPC key group information transaction.read: Read transaction information transaction.withdraw: Make withdrawals transaction.estimate_fee: Estimate transaction fee transaction.contract_call: Initiate contract calls transaction.message_sign: Initiate message signings transaction.stake: Stake assets transaction.unstake: Unstake assets transaction.unstake_withdraw: Withdraw unstaked assets transaction.manage: Manage ongoing transactions transaction.update: Update transaction notes travel_rule.read: Read travel rule information travel_rule.edit: Edit travel rule information webhook.read: Read webhook URLs/events webhook.edit: Edit webhook URLs webhook.resend: Resend webhook events payment_orders_payin.create: Create pay-in order payment_orders_payin.read: Read pay-in order information payment_orders_payin.update: Update pay-in order payment_orders_refund.create: Create payment refund order payment_orders_refund.read: Read payment refund order information payment_settlement.create: Create payment settlement request payment_settlement.read: Read payment settlement request information payment_merchant.create: Create payment merchant payment_merchant.read: Read payment merchant information payment_merchant.update: Update payment merchant payment_forced_sweep.create: Create payment force sweep request payment_forced_sweep.read: Read payment force sweep request information compliance_funds.refund: Refund compliance funds request compliance_funds.isolate: Isolate compliance funds request compliance_funds.unfreeze: Unfreeze compliance funds request compliance_funds.read: Read compliance funds request information compliance_kyt_review.update: Update KYT review status compliance_kyt_decisions.update: Update KYT decision status compliance_kyt_status.read: Read KYT screening status compliance_kya_screenings.create: Create KYA address screening requests compliance_kya_screenings.read: Read KYA address screening results ````