Qfex user API
The user API from Qfex — 15 operation(s) for user.
Qfex user API is one of 5 APIs that Qfex publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include user. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.
This API exposes 16 operations across 15 paths, and defines 26 schemas. It is described by OpenAPI 3.1.0, at version 0.1.0.
Requests are made against a single base URL, https://api.qfex.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 4
Qfex user API declares
4 security schemes
for authenticating requests.
An API key is passed in the header as x-qfex-hmac-signature (HMACSignature).
An API key is passed in the header as x-qfex-nonce (Nonce).
An API key is passed in the header as x-qfex-public-key (PublicKey).
An API key is passed in the header as x-qfex-timestamp (Timestamp).
HMACSignature— HMAC-SHA256 signature (hex-encoded).Nonce— Unique request nonce (hex encoded, max 100 characters).PublicKey— QFEX API Authentication requires these headers: - x-qfex-public-key: Your public API key - x-qfex-hmac-signature: HMAC signature of the request (hex encoded) -…Timestamp— Unix timestamp (seconds since epoch).
Paths & Operations 16
Across 15 paths, the API surfaces 16 operations — 13 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.
Schemas 26
The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are HistoricOrder (16 properties), HistoricTwap (14 properties), Trade (12 properties), UserVolumeResponseBody (11 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Qfex 4
Other APIs Qfex publishes across the network.