NiceHash API
★ Only Publicly Available OpenAPI DocumentFinanceBankingapiKey31 EndpointsREST
For Agents
Place and manage NiceHash hashpower orders, query mining pools, read exchange market data, and move funds between accounts across 31 endpoints under api2.nicehash.com.
Use for: Place a buy order for SHA-256 hashpower at a target price, Cancel an existing hashpower order, Get the current global mining stats across all algorithms, Refill a running hashpower order with more funds
Not supported: Does not handle mining-rig configuration, electricity billing, or fiat on-ramps — use for NiceHash hashpower marketplace, exchange, and account operations only.
Jentic publishes the only available OpenAPI specification for NiceHash API, keeping it validated and agent-ready. NiceHash is a crypto-mining marketplace that connects miners selling hashing power to buyers placing hashpower orders against any supported algorithm. The API exposes public market data (active orders, multi-algorithm stats, supported currencies and algorithms), private hashpower marketplace operations (place, refill, cancel, and re-price orders), pool configuration, exchange trading data (trades, candlesticks, order book), and account and wallet operations including withdrawals.
Install Jentic One Beta
Connect the NiceHash API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NiceHash API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with NiceHash API.
Read live global hashpower stats by algorithm through /main/api/v2/public/stats/global/current/
Place a buyer hashpower order through POST /main/api/v2/hashpower/order/
Refill or update price on an existing hashpower order through /main/api/v2/hashpower/order/{orderId}/refill/ and /updatePriceAndLimit/
Cancel a hashpower order before it expires through DELETE /main/api/v2/hashpower/order/{orderId}
Inspect account balances per currency through /main/api/v2/accounting/account2/{currency}
Initiate a withdrawal to a registered address through POST /main/api/v2/accounting/withdrawal/
Read exchange order book and candlesticks through /exchange/api/v2/orderbook and /exchange/api/v2/candlesticks
Use Cases
Patterns agents use NiceHash API for, with concrete tasks.
★ Programmatic hashpower buying
A buyer can run a strategy that places, re-prices, and cancels hashpower orders based on the live NiceHash order book and external coin profitability feeds. POST /main/api/v2/hashpower/order/ creates the order, /updatePriceAndLimit/ adjusts the bid as market depth shifts, and DELETE cancels it once the run completes. The strategy can refill running orders without restarting them.
POST a hashpower order on the SCRYPT algorithm with a price of 0.5 BTC/PH/day for 24 hours, then call /updatePriceAndLimit/ if the order book moves more than 5%.
Treasury and balance reconciliation
Operations and finance teams need to reconcile NiceHash balances against their internal ledgers. /main/api/v2/accounting/accounts2/ returns the full multi-currency balance sheet; /accounting/account2/{currency} drills into one asset; POST /accounting/withdrawal/ moves funds out to a pre-approved address. The X-Auth API-key header keeps each call scoped to a single account.
Call GET /main/api/v2/accounting/account2/BTC and post the available balance to a finance Slack channel each morning.
Exchange market data ingestion
Quant teams can pull NiceHash exchange trades, candlesticks, and the order book into a market-data warehouse. /exchange/api/v2/trades and /candlesticks provide historical fills and OHLC, while /orderbook returns live depth — together enough to build a basic pricing or arbitrage signal.
Call GET /exchange/api/v2/candlesticks?market=BTCUSDT&resolution=1440 and store the daily candles in a Postgres table.
AI agent crypto mining operations
An AI ops agent can monitor active hashpower orders, refill them when they near depletion, and cancel underperforming runs. Through Jentic, the agent searches by intent and Jentic returns the right NiceHash endpoint with its schema. The X-Auth signed key never enters the agent's chat context.
Search Jentic for 'cancel a hashpower order', load the DELETE /main/api/v2/hashpower/order/{orderId} schema, and execute it for the order ID returned by /myOrders.
Key Endpoints
31 endpoints — jentic publishes the only available openapi specification for nicehash api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/main/api/v2/hashpower/order/
Create a new hashpower order
DELETE
/main/api/v2/hashpower/order/{orderId}
Cancel a hashpower order
POST
/main/api/v2/hashpower/order/{orderId}/refill/
Refill an existing hashpower order
GET
/main/api/v2/hashpower/myOrders
List the caller's hashpower orders
GET
/main/api/v2/accounting/accounts2/
Get balances for every supported currency
POST
/main/api/v2/accounting/withdrawal/
Create a withdrawal to a registered address
GET
/exchange/api/v2/orderbook
Get the live exchange order book for a market
GET
/main/api/v2/public/stats/global/current/
Get current global hashpower stats
POST
/main/api/v2/hashpower/order/
Create a new hashpower order
DELETE
/main/api/v2/hashpower/order/{orderId}
Cancel a hashpower order
POST
/main/api/v2/hashpower/order/{orderId}/refill/
Refill an existing hashpower order
GET
/main/api/v2/hashpower/myOrders
List the caller's hashpower orders
GET
/main/api/v2/accounting/accounts2/
Get balances for every supported currency
POST
/main/api/v2/accounting/withdrawal/
Create a withdrawal to a registered address
GET
/exchange/api/v2/orderbook
Get the live exchange order book for a market
GET
/main/api/v2/public/stats/global/current/
Get current global hashpower stats
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
NiceHash X-Auth API keys are stored encrypted in the Jentic vault. Agents call hashpower and accounting endpoints via Jentic, which signs requests; raw keys never enter the agent's chat context.
Intent-based discovery
Agents search Jentic by intent (e.g. 'place a hashpower order') and Jentic returns the matching NiceHash endpoint with its input schema for direct execution.
Time to first call
Direct NiceHash integration: 2-4 days to handle X-Auth signing, error retries, and balance reconciliation. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using NiceHash API through Jentic.
Why is there no official OpenAPI spec for NiceHash API?
NiceHash does not publish a maintained OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call NiceHash API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the NiceHash API use?
NiceHash uses an apiKey scheme passed in the X-Auth request header. The key is signed against organisation, API key, and timestamp values per NiceHash's signing rules. Through Jentic, the X-Auth key is stored encrypted in the vault and never enters the agent's context.
Can I cancel a hashpower order via the API?
Yes. Call DELETE /main/api/v2/hashpower/order/{orderId} with the order ID returned from /main/api/v2/hashpower/myOrders. The order is cancelled immediately and any unspent balance is returned to the buyer's account.
What are the rate limits for the NiceHash API?
NiceHash applies rate limits per API key and per IP, but does not publish exact thresholds in the OpenAPI spec. Expect HTTP 429 responses if a single key issues sustained heavy traffic; back off and retry after the indicated cooldown.
How do I place a hashpower order through Jentic?
Run pip install jentic, then search Jentic for 'place a hashpower order'. Load the POST /main/api/v2/hashpower/order/ schema, supply algorithm, market, price, and limit fields, and execute. Jentic signs the X-Auth header for you.
Is the NiceHash API free to use?
API access is free for NiceHash account holders. Trades, hashpower orders, and withdrawals incur the usual NiceHash fees published on the marketplace; the API itself does not add a separate charge.
GET STARTED