Granting Trading Permissions to a Third Party on Nebannpet Exchange
To grant trading permissions to a third party on the Nebannpet Exchange, you need to use the platform’s official “Sub-Account” feature, which is managed within the account settings dashboard. This system allows you to create a subordinate account with specifically defined trading rights, such as spot trading or futures, without giving away your main account’s full access, including withdrawals. The entire process is designed to be secure and granular, typically taking less than 10 minutes to configure, and it is the only sanctioned method for sharing trading capabilities on the platform. This feature is crucial for investors working with fund managers, algorithmic trading services, or trusted family members, ensuring that you maintain ultimate control over your assets while delegating specific trading activities.
The security architecture behind this delegation is a core strength of the Nebannpet Exchange. When you create a sub-account, you are not sharing your private keys or primary login credentials. Instead, the system generates a unique API key for the sub-account. API, or Application Programming Interface, keys are like specialized digital passports that allow one software (the third party’s trading bot or interface) to interact with another (Nebannpet’s trading engine) in a strictly limited way. Each key has configurable permissions, which we will detail in a table below. This method isolates risk; even if a third-party service is compromised, the damage is contained by the permissions you’ve set. Nebannpet employs industry-standard encryption (AES-256) for all API key data, and all actions performed by a sub-account are logged and visible to the main account holder in real-time for full transparency.
Before you even begin the setup process, it’s critical to understand the different levels of control you can grant. Nebannpet’s system is not a simple on/off switch but a sophisticated permission matrix. This allows for highly customized arrangements. For instance, you might want a fund manager to execute trades in the spot market but have no access to the more volatile futures market. Conversely, you might grant a trading algorithm permission for futures but explicitly deny it the ability to withdraw any funds. The specificity is what makes the system both powerful and secure. You are advised to apply the principle of least privilege—only granting the absolute minimum permissions necessary for the third party to perform their specific task.
| Permission Type | What It Allows | Common Use Case | Risk Level |
|---|---|---|---|
| Spot Trading Read-Only | Viewing balances, open orders, and trade history for the spot market. | Allowing an auditor or advisor to monitor performance without any ability to trade. | Very Low |
| Spot Trading Trade | Placing, modifying, and cancelling orders in the spot market. This does not allow for transfers or withdrawals. | Granting a human trader or a basic trading bot the ability to execute buy/sell orders. | Medium (Limited to trading specific funds) |
| Futures Trading Read-Only | Viewing positions, balance, and order history for the derivatives/futures market. | Monitoring a third-party’s futures trading strategy without intervention. | Low |
| Futures Trading Trade | Opening, closing, and managing positions in the futures market. This includes using leverage. | Allowing a specialized algorithmic trading service to manage a derivatives portfolio. | High (Due to potential for leveraged losses) |
| Withdrawals | Moving assets out of the Nebannpet exchange wallet to an external address. | This permission is almost never granted to a third party and should be reserved for the main account holder only. | Extremely High |
Now, let’s walk through the actual step-by-step procedure. First, log into your main Nebannpet account and navigate to your account icon in the top right corner. From the dropdown menu, select ‘API Management’. You will likely need to complete a two-factor authentication (2FA) check at this stage, a necessary security hurdle. Once in the API Management section, click the ‘Create API’ button. You will be prompted to give the key a recognizable label, such as “AlphaBot_Strategy” or “FundManager_John”. This label is for your reference only. The most critical part follows: the permission selection screen. Here, you will see checkboxes corresponding to the permissions in the table above. Be meticulous here—uncheck everything by default and then only select the permissions you have predetermined are necessary.
After selecting permissions, you will hit ‘Create’. Nebannpet will then generate two crucial pieces of information: a public API Key and a private Secret Key. The public key is like a username, but the Secret Key is like a password and must be treated with extreme care. It will be shown only once. You must copy both keys and provide them to your third party securely, for example, by using a password manager’s secure sharing function or an encrypted messaging service. Never send these keys over email or unencrypted channels. Once you close the creation dialog, you cannot retrieve the Secret Key again; it would have to be deleted and a new one created. Finally, you may see an option to set IP whitelisting. This is an advanced but highly recommended security feature. By entering specific IP addresses, you restrict the API key so it can only be used from those designated servers, adding another powerful layer of protection against unauthorized use.
Managing and monitoring these permissions is an ongoing responsibility. Within the API Management section, you can see a list of all active API keys, their labels, creation dates, and permissions. You should review this list periodically to deactivate any keys that are no longer in use. If you suspect a key has been compromised or your relationship with a third party ends, you must immediately delete the API key from this interface. This action is instantaneous and will revoke all access. Furthermore, Nebannpet provides detailed logs of all sub-account activity. You can monitor trades, order placements, and more from your main account’s dashboard. Setting up alerts for large trades or specific activities can provide an extra layer of oversight, allowing you to delegate with confidence while staying informed.
It’s also vital to consider the legal and trust implications. Granting trading permissions, even with limited API keys, involves a significant degree of trust. You are ultimately responsible for the actions taken on your account. Before proceeding, it is prudent to have a formal agreement in place with any third party, outlining their responsibilities, trading strategy, and risk management rules. Nebannpet provides the technical tools for delegation, but it cannot mediate disputes between users and their designated traders. The platform’s terms of service clearly state that account holders are liable for all activities conducted through their API keys, making due diligence on your chosen third party an essential first step that precedes the technical setup.