BTSE
BTSE is a global cryptocurrency exchange offering spot, perpetual futures, OTC, earn and wallet services. Its developer program at docs.btse.com publishes OpenAPI 3 contracts for the Markets, Spot, Futures, Wallet, Earn and OTC REST APIs, AsyncAPI contracts for its WebSocket streams, a FIX protocol interface, HMAC-SHA384 request signing, and a testnet at testapi.btse.io.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles BTSE the way a machine reads it — 58 machine-readable artifacts across 16 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — BTSE scores 55.6/100 (strong), with a separate agent-readiness read of 37/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-17 · rubric v0.24.0
Put this on your own site. The badge is drawn live from BTSE's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/btse/"
title="BTSE on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/btse.svg"
alt="BTSE Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/btse/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/btse/"
title="BTSE on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/btse/card.svg"
alt="BTSE Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile BTSE
Each block below is one kind of artifact we hold for BTSE. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 8
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
BTSE Account API
Requires API key with Read permission
BTSE Earn API
Investment product endpoints
BTSE Markets API
Public market data shared by spot and futures markets
BTSE OTC API
OTC trading endpoints
BTSE Trade API
Requires API key with Trading permission
BTSE Trade V3 API
The Trade V3 API from BTSE — 11 operation(s) for trade v3.
BTSE Trade V4 API
The Trade V4 API from BTSE — 7 operation(s) for trade v4.
BTSE Wallet API
Requires API key with Read or Transfer permission
Scroll within the panel for all 8 ·
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Btse Rate Limits
RATE LIMITSEvent Specifications 3
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Futures WebSocket API
Futures WebSocket streams for real-time market data and private user events. **OSS Endpoint (Orderbook):** `wss://ws.btse.com/ws/oss/futures` **Main Endpoint:** `wss://ws.btse.c...
ASYNCAPIOTC WebSocket API
OTC WebSocket stream for real-time OTC quote data. **Production Endpoint:** `wss://ws.btse.com/ws/otc` **Testnet Endpoint:** `wss://testws.btse.io/ws/otc` **Authentication:** Pr...
ASYNCAPISpot WebSocket API
Spot WebSocket streams for real-time market data and private user events. **OSS Endpoint (Orderbook):** `wss://ws.btse.com/ws/oss/spot` **Main Endpoint:** `wss://ws.btse.com/ws/...
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Btse Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
BTSE API Rules
SPECTRALJSON Schema 41
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccountFee
JSON SCHEMAAmendOrderRequest
JSON SCHEMAAmendOrderResp
JSON SCHEMAAssetExchangeRateResponse
JSON SCHEMAClosePositionResp
JSON SCHEMAConditional
JSON SCHEMAConvertRequest
JSON SCHEMACreateAddressRequest
JSON SCHEMACreateOrderRequest
JSON SCHEMADefaultResponse
JSON SCHEMADepositInvestmentRequest
JSON SCHEMAExchangeInfoResponse
JSON SCHEMAFundingRateHistoryResponse
JSON SCHEMAFuturesOrderResponse
JSON SCHEMAFuturesUserTrade
JSON SCHEMAInvestmentHistoryResponse
JSON SCHEMAInvestmentOrder
JSON SCHEMAInvestmentProduct
JSON SCHEMAMarketRiskLimitArrayResponse
JSON SCHEMAMarketsResponse
JSON SCHEMAOHLCVResponse
JSON SCHEMAOpenOrderResponse
JSON SCHEMAOrderResp
JSON SCHEMAOrderResponse
JSON SCHEMAOTCAcceptQuoteRequest
JSON SCHEMAOTCMarketResponse
JSON SCHEMAOTCQuoteResponse
JSON SCHEMAOTCRequestQuoteRequest
JSON SCHEMAPlaceOrderResp
JSON SCHEMAPositionResp
JSON SCHEMAPosition
JSON SCHEMAQueryOrderResp
JSON SCHEMAQueryOrderResponse
JSON SCHEMARedeemInvestmentRequest
JSON SCHEMARenewInvestmentRequest
JSON SCHEMATicker24HrFullArrayResponse
JSON SCHEMATradeHistoryResp
JSON SCHEMATransferRequest
JSON SCHEMATwap
JSON SCHEMAUserTrade
JSON SCHEMAWithdrawRequest
JSON SCHEMAScroll within the panel for all 41 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for BTSE — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 5
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/btse · machine-readable index on apis.io
This is an independent, third-party profile of BTSE, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.