binance-sdk-nft

Binance Python NFT SDK

This is a client library for the Binance NFT SDK API, enabling developers to interact programmatically with Binance's NFT trading platform. The library provides tools to launch and trade NFTs through the REST API:

• REST API

Table of Contents

• Supported Features
• Installation
• Documentation
• REST APIs
• Testing
• Migration Guide
• Contributing
• Licence

Supported Features

• REST API Endpoints:
  • /sapi/v1/nft/*
• Inclusion of test cases and examples for quick onboarding.

Installation

To use this library, ensure your environment is running Python version 3.9 or later.

pip install binance-sdk-nft

Documentation

For detailed information, refer to the Binance API Documentation.

REST APIs

All REST API endpoints are available through the rest_api module. The REST API enables you to fetch market data, manage trades, and access account information. Note that some endpoints require authentication using your Binance API credentials.

from binance_common.configuration import ConfigurationRestAPI
from binance_common.constants import NFT_REST_API_PROD_URL
from binance_sdk_nft.nft import NFT
from binance_sdk_nft.rest_api.models import GetNFTAssetResponse

logging.basicConfig(level=logging.INFO)
configuration = ConfigurationRestAPI(api_key="your-api-key", api_secret="your-api-secret", base_path=NFT_REST_API_PROD_URL)

client = NFT(config_rest_api=configuration)

try:
    response = client.rest_api.get_nft_asset()

    data: GetNFTAssetResponse = response.data()
    logging.info(f"get_nft_asset() response: {data}")
except Exception as e:
    logging.error(f"get_nft_asset() error: {e}")

More examples can be found in the examples/rest_api folder.

Configuration Options

The REST API supports the following advanced configuration options:

• timeout: Timeout for requests in milliseconds (default: 1000 ms).
• proxy: Proxy configuration:
  • host: Proxy server hostname.
  • port: Proxy server port.
  • protocol: Proxy protocol (http or https).
  • auth: Proxy authentication credentials:
    • username: Proxy username.
    • password: Proxy password.
• keep_alive: Enable HTTP keep-alive (default: true).
• compression: Enable response compression (default: true).
• retries: Number of retry attempts for failed requests (default: 3).
• backoff: Delay in milliseconds between retries (default: 1000 ms).
• https_agent: Custom HTTPS agent for advanced TLS configuration.
• private_key: RSA or ED25519 private key for authentication.
• private_key_passphrase: Passphrase for the private key, if encrypted.

Timeout

You can configure a timeout for requests in milliseconds. If the request exceeds the specified timeout, it will be aborted. See the Timeout example for detailed usage.

Proxy

The REST API supports HTTP/HTTPS proxy configurations. See the Proxy example for detailed usage.

Keep-Alive

Enable HTTP keep-alive for persistent connections. See the Keep-Alive example for detailed usage.

Compression

Enable or disable response compression. See the Compression example for detailed usage.

Retries

Configure the number of retry attempts and delay in milliseconds between retries for failed requests. See the Retries example for detailed usage.

HTTPS Agent

Customize the HTTPS agent for advanced TLS configurations. See the HTTPS Agent example for detailed usage.

Key Pair Based Authentication

The REST API supports key pair-based authentication for secure communication. You can use RSA or ED25519 keys for signing requests. See the Key Pair Based Authentication example for detailed usage.

Certificate Pinning

To enhance security, you can use certificate pinning with the https_agent option in the configuration. This ensures the client only communicates with servers using specific certificates. See the Certificate Pinning example for detailed usage.

Error Handling

The REST API provides detailed error types to help you handle issues effectively:

• ClientError: Represents an error that occurred in the SDK client.
• RequiredError: Thrown when a required parameter is missing or undefined.
• UnauthorizedError: Indicates missing or invalid authentication credentials.
• ForbiddenError: Access to the requested resource is forbidden.
• TooManyRequestsError: Rate limit exceeded.
• RateLimitBanError: IP address banned for exceeding rate limits.
• ServerError: Internal server error, optionally includes a status code.
• NetworkError: Issues with network connectivity.
• NotFoundError: Resource not found.
• BadRequestError: Invalid request or one that cannot be served.

See the Error Handling example for detailed usage.

If base_path is not provided, it defaults to https://api.binance.com.

Testing

To run the tests, ensure you have Poetry installed, then execute the following commands:

poetry install
poetry run pytest ./tests

The tests cover:

• REST API endpoints
• Error handling
• Edge cases

Migration Guide

If you are upgrading to the new modularized structure, refer to the Migration Guide for detailed steps.

Contributing

Contributions are welcome!

Since this repository contains auto-generated code, we encourage you to start by opening a GitHub issue to discuss your ideas or suggest improvements. This helps ensure that changes align with the project's goals and auto-generation processes.

To contribute:

• Open a GitHub issue describing your suggestion or the bug you've identified.
• If it's determined that changes are necessary, the maintainers will merge the changes into the main branch.

Please ensure that all tests pass if you're making a direct contribution. Submit a pull request only after discussing and confirming the change.

Thank you for your contributions!

Licence

This project is licensed under the MIT License. See the LICENCE file for details.