Bitteam

Every endpoint in bitteam's api definition is exposed as an implicit method — a thin, generated wrapper around the raw exchange endpoint. Use these for exchange-specific functionality the CCXT API does not cover.

These methods are available in every CCXT language — TypeScript, JavaScript, Python, PHP, C# and Go. Call them by the camelCase name shown in the tables below (e.g. historyGetApiTwHistoryPairNameResolution); the snake_case alias (history_get_api_tw_history_pairname_resolution) also works in JavaScript, Python and PHP, and Go uses the PascalCase form (HistoryGetApiTwHistoryPairNameResolution). Switch tabs for the call in each language:

JavaScript

const bitteam = new ccxt.bitteam ();
const response = await bitteam.historyGetApiTwHistoryPairNameResolution (params);

TypeScript

import ccxt from 'ccxt';
const bitteam = new ccxt.bitteam ();
const response = await bitteam.historyGetApiTwHistoryPairNameResolution (params);

Python

import ccxt
bitteam = ccxt.bitteam()
response = bitteam.history_get_api_tw_history_pairname_resolution(params)

PHP

$bitteam = new \ccxt\bitteam();
$response = $bitteam->history_get_api_tw_history_pairname_resolution($params);

C#

using ccxt;
var bitteam = new Bitteam();
var response = await bitteam.historyGetApiTwHistoryPairNameResolution(parameters);

Go

bitteam := ccxt.NewBitteam(nil)
response := <-bitteam.HistoryGetApiTwHistoryPairNameResolution(params)

Path parameters wrapped in {} (e.g. {pair}) are substituted from params; everything else in params is sent as the query string or request body. Cost is the rate-limiter weight of each call.

📚 Official bitteam API documentation: bit.team

25 implicit endpoints across 3 access groups.

history

Base URL: https://history.bit.team

public

Base URL: https://bit.team

private

Base URL: https://bit.team