Version: 1.2.0
DLTM Derivatives API
REST API for derivatives trading on DLT Markets.
The API abstracts exchange-specific details behind a unified interface using canonical instrument symbols.
Authentication
All requests require ed25519 signature authentication via three headers:
| Header | Description |
|---|---|
X-Public-Key | Your public key, hex-encoded. |
X-Nonce | Integer timestamp (e.g. milliseconds). Must be strictly increasing — each value must be greater than the last. |
X-Signature | ed25519 signature of the request, hex-encoded. |
Signature construction:
message = {METHOD}{uri}{body}{nonce}
METHOD— HTTP method in uppercase (e.g.POST)uri— Full path including query string, excluding domain (e.g./v1/orders)body— JSON request body for POST/PUT/PATCH; empty string otherwisenonce— Same nanosecond timestamp sent inX-Nonce
Example (POST order):
POST/v1/orders{"customer_code":"3a034186-...","instrument_symbol":"BTCUSDC_PERP",...}1531816217872000000
Sign the resulting message with your ed25519 private key and hex-encode the result.
Conventions
- Decimal values are represented as strings to avoid floating-point precision issues
- Identifiers use UUID format and are referred to as
code(e.g.,order_code) - Timestamps in responses use ISO 8601 format (
date-time). Date range query parameters (start,end) use milliseconds since epoch. - Pagination uses cursor-based pagination with
after,before, andpage_sizequery parameters - List responses follow the format
{records: [Item], response_metadata: {has_next, has_previous, start_cursor, end_cursor}} - Sorting uses the
sortquery parameter with valuesascordesc(defaultasc), where supported
Rate Limiting
API requests are subject to rate limiting. When the limit is exceeded, the API returns
a 429 Too Many Requests response with a Retry-After header.
Base URLs
| Environment | URL |
|---|---|
| Production | https://derivatives.api.dlt-finance.com/v1 |
| Integration | https://derivatives.api.dlt-int-01.int.dlt-finance.com/v1 |
Authentication
- API Key: ApiTokenAuth
ed25519 API key. Must be accompanied by X-Nonce and X-Signature headers.
See Authentication section for signature construction details.
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | X-Public-Key |