🇺🇸English

HTX USDT-M Futures Skill

USDT-M Futures trading on HTX using authenticated and public API endpoints. Return the result in JSON format.

Base URLs

• Mainnet: https://api.hbdm.com
• Mainnet (AWS): https://api.hbdm.vn

Quick Reference

Complete API endpoints for HTX USDT-M Futures. All endpoints use base URL https://api.hbdm.com (or https://api.hbdm.vn for AWS).

Reference Data

Market Data

Account Interface

Trade Interface

Strategy Order Interface

Transferring Interface

Parameters

Common Parameters

Contract & Symbol

• contract_code : Contract code (e.g., BTC-USDT, ETH-USDT)
• symbol : Symbol name
• pair : Trading pair (e.g., BTC-USDT)
• contract_type : Contract type (swap, this_week, next_week, quarter, next_quarter)
• business_type : Business type (futures, swap, all)

Account & Margin

• margin_account : Margin account identifier
• margin_mode : Margin mode (cross, isolated)
• margin_asset : Margin asset (e.g., USDT)
• account_type : Account type

Order Parameters

• order_id : Order ID (can be comma-separated for multiple orders)
• client_order_id : Client-defined order ID
• order_source : Order source
• order_type : Order type
• order_price_type : Order price type (limit, optimal_5, optimal_10, optimal_20, post_only, fok, ioc, etc.)
• direction : Transaction direction (buy, sell)
• offset : Offset direction (open, close, both)
• volume : Order volume (quantity in contracts)
• price : Order price
• lever_rate : Leverage rate
• reduce_only : Reduce only flag (0: no, 1: yes)

Trigger Order Parameters

• trigger_type : Trigger type (ge: greater than or equal, le: less than or equal)
• trigger_price : Trigger price
• triggered_price : The price when trigger order was executed

Take-Profit & Stop-Loss Parameters

• tp_trigger_price : Trigger price of take-profit order
• tp_order_price : Order price of take-profit order
• tp_order_price_type : Order type of take-profit order
• sl_trigger_price : Trigger price of stop-loss order
• sl_order_price : Order price of stop-loss order
• sl_order_price_type : Order type of stop-loss order
• price_protect : Price protection (boolean)

Trailing Order Parameters

• callback_rate : Callback rate for trailing orders
• active_price : Active price for trailing orders
• is_active : Whether the active price is activated

Query Parameters

• page_index : Page number (default: 1)
• page_size : Page size (default: 20, max: 50)
• start_time : Start time (Unix timestamp in milliseconds)
• end_time : End time (Unix timestamp in milliseconds)
• create_date : Number of days
• direct : Search direction (NEXT: ascending, PREV: descending)
• from_id : Starting ID for pagination
• sort_by : Sort field (descending order)

Sub-account Parameters

• sub_uid : Sub-account UID
• sub_auth : Sub-account authorization (0: disable, 1: enable)

Transfer Parameters

• from : Source account (e.g., spot, linear-swap)
• to : Destination account (e.g., spot, linear-swap)
• currency : Currency to transfer
• amount : Transfer amount
• from_margin_account : Source margin account
• to_margin_account : Destination margin account

Market Data Parameters

• period : K-line period (1min, 5min, 15min, 30min, 60min, 4hour, 1day, 1mon, 1week, 1year)
• type : Depth type (step0-step19)
• size : Number of records to return

Other Parameters

• trade_type : Trade type (0: all, 1: open long, 2: open short, 3: close short, 4: close long)
• status : Order status (multiple statuses can be comma-separated)
• self_match_prevent : Self-match prevention flag
• self_match_prevent_new : Prevent self-trading

Enums

Order Types

• order_price_type : limit, optimal_5, optimal_10, optimal_20, post_only, fok, ioc, opponent, lightning, optimal_5_fok, optimal_5_ioc, optimal_10_fok, optimal_10_ioc, optimal_20_fok, optimal_20_ioc, opponent_ioc, opponent_fok

Order States

• status : submitted (3), partial-filled (4), partial-canceled (5), filled (6), canceled (7), ready to submit (1), accepted (2)

Direction & Offset

• direction : buy, sell
• offset : open, close, both

Margin Mode

• margin_mode : isolated, cross

Contract Type

• contract_type : swap (perpetual), this_week, next_week, quarter (current quarter), next_quarter

Position Mode

• position_mode : dual_side (hedge mode), single_side (one-way mode)

Authentication

For endpoints that require authentication, you will need to provide HTX API credentials.

Required credentials:

• apiKey : Your HTX API key
• secretKey : Your HTX API secret (for signing)

All authenticated endpoints require HMAC SHA256 signature:

1. Create the pre-sign string in the following order:

   • HTTP method (GET/POST) + "\n"
   • API host (e.g., api.hbdm.com) + "\n"
   • API path (e.g., /linear-swap-api/v1/swap_order) + "\n"
   • Sorted query string parameters

2. Append required parameters to all authenticated requests:

   • AccessKeyId: Your API key
   • SignatureMethod: HmacSHA256
   • SignatureVersion: 2
   • Timestamp: UTC timestamp in format yyyy-MM-ddTHH:mm:ss

3. Sign the pre-sign string with secretKey using HMAC SHA256

4. Append signature to query string as Signature parameter

5. For POST requests, also include signature in the URL query string

Example pre-sign string:

POST\\n
api.hbdm.com\\n
/linear-swap-api/v1/swap_order\\n
AccessKeyId=xxx&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2017-05-11T15:19:30

Security

Share Credentials

Users can provide HTX API credentials by sending a file where the content is in the following format:

fe45419a...xyz
secretabc...key

Never Display Full Secrets

When showing credentials to users:

• API Key: Show first 5 + last 4 characters: fe45419a...xyz
• Secret Key: Always mask, show only last 5: ***...key1

Example response when asked for credentials:

Account: main
API Key: fe45419a...xyz
Secret: ***...key1
Environment: Mainnet

Listing Accounts

When listing accounts, show names and environment only — never keys:

HTX Accounts:
* main (Mainnet)
* trading (Mainnet - AWS)

Transactions in Mainnet

When performing transactions in mainnet, always confirm with the user before proceeding by asking them to write "CONFIRM" to proceed.

HTX Accounts

main

• API Key: your_mainnet_api_key
• Secret: your_mainnet_secret
• Environment: https://api.hbdm.com
• Description: Primary USDT-M Futures trading account

trading

• API Key: your_aws_api_key
• Secret: your_aws_secret
• Environment: https://api.hbdm.vn
• Description: AWS optimized USDT-M Futures trading

TOOLS.md Structure

## HTX Accounts

### main
- API Key: fe45419a...xyz
- Secret: secretabc...key
- Environment: https://api.hbdm.com
- Description: Primary USDT-M Futures trading account

### trading
- API Key: test456...abc
- Secret: testsecret...xyz
- Environment: https://api.hbdm.vn
- Description: AWS optimized USDT-M Futures trading

Agent Behavior

1. Credentials requested : Mask secrets (show last 5 chars only)
2. Listing accounts : Show names and environment, never keys
3. Account selection : Ask if ambiguous, default to main
4. When doing a transaction in mainnet , confirm with user before by asking to write "CONFIRM" to proceed
5. New credentials : Prompt for name, environment

Adding New Accounts

When user provides new credentials:

• Ask for account name
• Ask: Which environment (Mainnet or Mainnet-AWS)
• Store in TOOLS.md with masked display confirmation

User Agent Header

Include User-Agent header with the following string: htx-usdt-m-futures/1.0.0 (Skill)

Important Notes

• All timestamps are in Unix milliseconds unless specified otherwise
• Contract codes should use uppercase (e.g., BTC-USDT, not btc-usdt)
• For market buy orders, the volume parameter represents the number of contracts
• Account ID must be obtained from appropriate endpoints before trading
• Rate limits apply - see HTX API documentation for details
• Signature must be calculated for every authenticated request
• Timestamp in signature must be within 1 minute of server time
• Both isolated margin and cross margin modes are supported
• Position modes: single_side (one-way) and dual_side (hedge)
• Always use the correct margin mode and margin account for operations
• For cross margin operations, use endpoints with "cross" in their path
• For isolated margin operations, use endpoints without "cross" in their path
• All request endpoints must match the endpoints specified in the documentation.

Weekly Installs

68

Repository

htx-exchange/ht…ills-hub

GitHub Stars

9

First Seen

12 days ago

Security Audits

Gen Agent Trust HubPassSocketPassSnykFail

Installed on

opencode68

codex68

kimi-cli67

gemini-cli67

amp67

cline67