Your next integration.
Powered by BitTools.

Your developer workspace

API access is available by request. Tell us about your application and expected usage; our team will create your key after review.

Your first request, in three steps.

curl "https://www.bittools.net/api/v1/prices?ids=bitcoin,ethereum&fiat=USD" \
  -H "Authorization: Bearer $BITTOOLS_API_KEY"

Keys belong in request headers, never in URLs. Documentation is public; data requests require authentication.

One key. Clear access.

Send Authorization: Bearer YOUR_API_KEY with every API request. Alternatively, use X-BT-API-Key: YOUR_API_KEY. If both are provided, X-BT-API-Key takes priority. Use server-side requests so your secret stays private.

New keys begin with btd_live_. Revoked or expired keys stop working immediately. Keys tied to an account stop working when that account is disabled. A valid key also needs permission for the endpoint you call.

Responses use success, data and meta; failed requests include error.message and error.status.

{
    "success": true,
    "data": {
        "bitcoin": {
            "price": 81000,
            "change_24h": 1.25,
            "market_cap": 1600000000000,
            "last_updated": "2026-10-09T00:00:00Z"
        }
    },
    "meta": {
        "api_version": "v1",
        "source": "BitTools",
        "generated_at": "2026-10-09T00:00:00Z",
        "response_time_ms": 8,
        "fiat": "USD"
    }
}

Example values are illustrative. Cached market data can be older than the response generation time; inspect last_updated.

Explore the endpoints.

Use cryptocurrency IDs such as bitcoin or ethereum, not ticker symbols. Fiat defaults to the site's configured currency. Unsupported fiat values fall back to that default. Lists accept 1–250 items per page.

The downloadable OpenAPI specification describes the response fields and can be imported into API clients.

Transaction accelerator

Discuss an accelerator API partnership

Send a Bitcoin transaction ID in a JSON object. A transaction ID is 64 hexadecimal characters. This endpoint submits an existing transaction; it does not request private keys or wallet seed phrases.

curl -X POST "https://www.bittools.net/api/v1/accelerator" \
  -H "Authorization: Bearer $BITTOOLS_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{"txid":"REPLACE_WITH_YOUR_64_CHARACTER_TRANSACTION_ID"}'

When a connected accelerator accepts the submission, the response is HTTP 202 with data.txid and data.status: submitted. Submitted does not mean confirmed; confirmation depends on the Bitcoin network. Requests can return 403 when accelerator access is disabled and 503 when the backend is unavailable.

Request body limit: 2 KB. Do not retry a submission automatically unless your integration knows it is safe to repeat.

Use your preferred language.

<?php
$key = getenv('BITTOOLS_API_KEY');
$ch = curl_init('https://www.bittools.net/api/v1/prices?ids=bitcoin&fiat=USD');
curl_setopt_array($ch, [
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_TIMEOUT => 15,
  CURLOPT_HTTPHEADER => ['Authorization: Bearer '.$key]
]);
$body = curl_exec($ch);
$status = curl_getinfo($ch, CURLINFO_HTTP_CODE);
if ($body === false) { throw new RuntimeException(curl_error($ch)); }
curl_close($ch);
$response = json_decode($body, true);
if ($status !== 200 || empty($response['success'])) {
  throw new RuntimeException('API request failed: '.$status);
}
print_r($response['data']);

const response = await fetch('https://www.bittools.net/api/v1/prices?ids=bitcoin&fiat=USD', {
  headers: { Authorization: `Bearer ${process.env.BITTOOLS_API_KEY}` }
});
const body = await response.json();
if (!response.ok || !body.success) throw new Error(body.error?.message || 'API request failed');
console.log(body.data);

import os, json
from urllib.request import Request, urlopen
from urllib.error import HTTPError
request = Request('https://www.bittools.net/api/v1/prices?ids=bitcoin&fiat=USD',
    headers={'Authorization': 'Bearer ' + os.environ['BITTOOLS_API_KEY']})
try:
    with urlopen(request, timeout=15) as response:
        body = json.load(response)
    if not body['success']:
        raise RuntimeError(body.get('error'))
    print(body['data'])
except HTTPError as error:
    raise RuntimeError(f'API request failed: {error.code}') from error

Know your limits.

Your assigned limits apply across market and accelerator requests. Default limits for new keys: 30 per minute and 1000 per day. Administrators may assign different limits.

Authenticated requests consume quota, including validation errors. Minute and day windows reset at UTC boundaries. Inspect X-RateLimit-Limit-Minute, X-RateLimit-Remaining-Minute, X-RateLimit-Limit-Day and X-RateLimit-Remaining-Day. A rate-limited response includes Retry-After for new portal keys.

Browser keys and public URL query tokens are not supported. CORS availability does not make a key safe to expose. Existing legacy market keys retain their original configured limits and windows.