Zaif

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

JavaScript

const zaif = new ccxt.zaif ();
const response = await zaif.publicGetDepthPair (params);

TypeScript

import ccxt from 'ccxt';
const zaif = new ccxt.zaif ();
const response = await zaif.publicGetDepthPair (params);

Python

import ccxt
zaif = ccxt.zaif()
response = zaif.public_get_depth_pair(params)

PHP

$zaif = new \ccxt\zaif();
$response = $zaif->public_get_depth_pair($params);

C#

using ccxt;
var zaif = new Zaif();
var response = await zaif.publicGetDepthPair(parameters);

Go

zaif := ccxt.NewZaif(nil)
response := <-zaif.PublicGetDepthPair(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 zaif API documentation: techbureau-api-document.readthedocs.io · corp.zaif.jp · corp.zaif.jp · npmjs.com · github.com

34 implicit endpoints across 5 access groups.

public

private

ecapi

tlapi

fapi