Tokocrypto

Every endpoint in tokocrypto'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. binanceGetPing); the snake_case alias (binance_get_ping) also works in JavaScript, Python and PHP, and Go uses the PascalCase form (BinanceGetPing). Switch tabs for the call in each language:

JavaScript

const tokocrypto = new ccxt.tokocrypto ();
const response = await tokocrypto.binanceGetPing (params);

TypeScript

import ccxt from 'ccxt';
const tokocrypto = new ccxt.tokocrypto ();
const response = await tokocrypto.binanceGetPing (params);

Python

import ccxt
tokocrypto = ccxt.tokocrypto()
response = tokocrypto.binance_get_ping(params)

PHP

$tokocrypto = new \ccxt\tokocrypto();
$response = $tokocrypto->binance_get_ping($params);

C#

using ccxt;
var tokocrypto = new Tokocrypto();
var response = await tokocrypto.binanceGetPing(parameters);

Go

tokocrypto := ccxt.NewTokocrypto(nil)
response := <-tokocrypto.BinanceGetPing(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 tokocrypto API documentation: tokocrypto.com

33 implicit endpoints across 3 access groups.

binance

public

private