Exchange Info
Market Definitions
Market Status Field
Authentication Headers
Endpoints, public
Statistics about the price of an asset during a specific time interval. Returned as an array of unnamed values to reduce size. Fields are: [ time (in seconds since epoch), open price, high price, low price, close price, volume (in RawUnits) ] Cached frequently to improve response time; provide 'Cache-Control: no-cache' header on request to pass through.
An error was encountered while processing the request.
Endpoints, authentication required
The API Key ID as specified in the API settings page.
Each API key has a corresponding access level that is set when the key is created.
- Read access only allows access to read HTTP methods (GET, HEAD, etc.).
- Write access allows access to all HTTP methods.
The API signature string authenticating this request.
The payload to be signed is the concatenation of the byte string cube.xyz and the current unix epoch timestamp in seconds converted into an 8-byte little-endian array. The signature is the HMAC-SHA256 digest of the payload using the secret key associated with the specified API key.
Implementation notes:
-
The signature is base-64 encoded with the 'standard' alphabet and padding.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ -
The timestamp should be encoded as 8-byte little-endian (array of bytes)
-
The secret key should be decoded from a hex string into a 32-byte array of bytes
The timestamp used for signature generation.
An error was encountered while processing the request.
The API Key ID as specified in the API settings page.
Each API key has a corresponding access level that is set when the key is created.
- Read access only allows access to read HTTP methods (GET, HEAD, etc.).
- Write access allows access to all HTTP methods.
The API signature string authenticating this request.
The payload to be signed is the concatenation of the byte string cube.xyz and the current unix epoch timestamp in seconds converted into an 8-byte little-endian array. The signature is the HMAC-SHA256 digest of the payload using the secret key associated with the specified API key.
Implementation notes:
-
The signature is base-64 encoded with the 'standard' alphabet and padding.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ -
The timestamp should be encoded as 8-byte little-endian (array of bytes)
-
The secret key should be decoded from a hex string into a 32-byte array of bytes
The timestamp used for signature generation.
An error was encountered while processing the request.
The API Key ID as specified in the API settings page.
Each API key has a corresponding access level that is set when the key is created.
- Read access only allows access to read HTTP methods (GET, HEAD, etc.).
- Write access allows access to all HTTP methods.
The API signature string authenticating this request.
The payload to be signed is the concatenation of the byte string cube.xyz and the current unix epoch timestamp in seconds converted into an 8-byte little-endian array. The signature is the HMAC-SHA256 digest of the payload using the secret key associated with the specified API key.
Implementation notes:
-
The signature is base-64 encoded with the 'standard' alphabet and padding.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ -
The timestamp should be encoded as 8-byte little-endian (array of bytes)
-
The secret key should be decoded from a hex string into a 32-byte array of bytes
The timestamp used for signature generation.
An error was encountered while processing the request.
The API Key ID as specified in the API settings page.
Each API key has a corresponding access level that is set when the key is created.
- Read access only allows access to read HTTP methods (GET, HEAD, etc.).
- Write access allows access to all HTTP methods.
The API signature string authenticating this request.
The payload to be signed is the concatenation of the byte string cube.xyz and the current unix epoch timestamp in seconds converted into an 8-byte little-endian array. The signature is the HMAC-SHA256 digest of the payload using the secret key associated with the specified API key.
Implementation notes:
-
The signature is base-64 encoded with the 'standard' alphabet and padding.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ -
The timestamp should be encoded as 8-byte little-endian (array of bytes)
-
The secret key should be decoded from a hex string into a 32-byte array of bytes
The timestamp used for signature generation.
An error was encountered while processing the request.
The API Key ID as specified in the API settings page.
Each API key has a corresponding access level that is set when the key is created.
- Read access only allows access to read HTTP methods (GET, HEAD, etc.).
- Write access allows access to all HTTP methods.
The API signature string authenticating this request.
The payload to be signed is the concatenation of the byte string cube.xyz and the current unix epoch timestamp in seconds converted into an 8-byte little-endian array. The signature is the HMAC-SHA256 digest of the payload using the secret key associated with the specified API key.
Implementation notes:
-
The signature is base-64 encoded with the 'standard' alphabet and padding.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ -
The timestamp should be encoded as 8-byte little-endian (array of bytes)
-
The secret key should be decoded from a hex string into a 32-byte array of bytes
The timestamp used for signature generation.
An error was encountered while processing the request.
The API Key ID as specified in the API settings page.
Each API key has a corresponding access level that is set when the key is created.
- Read access only allows access to read HTTP methods (GET, HEAD, etc.).
- Write access allows access to all HTTP methods.
The API signature string authenticating this request.
The payload to be signed is the concatenation of the byte string cube.xyz and the current unix epoch timestamp in seconds converted into an 8-byte little-endian array. The signature is the HMAC-SHA256 digest of the payload using the secret key associated with the specified API key.
Implementation notes:
-
The signature is base-64 encoded with the 'standard' alphabet and padding.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ -
The timestamp should be encoded as 8-byte little-endian (array of bytes)
-
The secret key should be decoded from a hex string into a 32-byte array of bytes
The timestamp used for signature generation.
An error was encountered while processing the request.
The API Key ID as specified in the API settings page.
Each API key has a corresponding access level that is set when the key is created.
- Read access only allows access to read HTTP methods (GET, HEAD, etc.).
- Write access allows access to all HTTP methods.
The API signature string authenticating this request.
The payload to be signed is the concatenation of the byte string cube.xyz and the current unix epoch timestamp in seconds converted into an 8-byte little-endian array. The signature is the HMAC-SHA256 digest of the payload using the secret key associated with the specified API key.
Implementation notes:
-
The signature is base-64 encoded with the 'standard' alphabet and padding.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ -
The timestamp should be encoded as 8-byte little-endian (array of bytes)
-
The secret key should be decoded from a hex string into a 32-byte array of bytes
The timestamp used for signature generation.
An error was encountered while processing the request.
The API Key ID as specified in the API settings page.
Each API key has a corresponding access level that is set when the key is created.
- Read access only allows access to read HTTP methods (GET, HEAD, etc.).
- Write access allows access to all HTTP methods.
The API signature string authenticating this request.
The payload to be signed is the concatenation of the byte string cube.xyz and the current unix epoch timestamp in seconds converted into an 8-byte little-endian array. The signature is the HMAC-SHA256 digest of the payload using the secret key associated with the specified API key.
Implementation notes:
-
The signature is base-64 encoded with the 'standard' alphabet and padding.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ -
The timestamp should be encoded as 8-byte little-endian (array of bytes)
-
The secret key should be decoded from a hex string into a 32-byte array of bytes
The timestamp used for signature generation.
An error was encountered while processing the request.
The API Key ID as specified in the API settings page.
Each API key has a corresponding access level that is set when the key is created.
- Read access only allows access to read HTTP methods (GET, HEAD, etc.).
- Write access allows access to all HTTP methods.
The API signature string authenticating this request.
The payload to be signed is the concatenation of the byte string cube.xyz and the current unix epoch timestamp in seconds converted into an 8-byte little-endian array. The signature is the HMAC-SHA256 digest of the payload using the secret key associated with the specified API key.
Implementation notes:
-
The signature is base-64 encoded with the 'standard' alphabet and padding.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ -
The timestamp should be encoded as 8-byte little-endian (array of bytes)
-
The secret key should be decoded from a hex string into a 32-byte array of bytes
The timestamp used for signature generation.
An error was encountered while processing the request.
The API Key ID as specified in the API settings page.
Each API key has a corresponding access level that is set when the key is created.
- Read access only allows access to read HTTP methods (GET, HEAD, etc.).
- Write access allows access to all HTTP methods.
The API signature string authenticating this request.
The payload to be signed is the concatenation of the byte string cube.xyz and the current unix epoch timestamp in seconds converted into an 8-byte little-endian array. The signature is the HMAC-SHA256 digest of the payload using the secret key associated with the specified API key.
Implementation notes:
-
The signature is base-64 encoded with the 'standard' alphabet and padding.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ -
The timestamp should be encoded as 8-byte little-endian (array of bytes)
-
The secret key should be decoded from a hex string into a 32-byte array of bytes
The timestamp used for signature generation.
An error was encountered while processing the request.
The API Key ID as specified in the API settings page.
Each API key has a corresponding access level that is set when the key is created.
- Read access only allows access to read HTTP methods (GET, HEAD, etc.).
- Write access allows access to all HTTP methods.
The API signature string authenticating this request.
The payload to be signed is the concatenation of the byte string cube.xyz and the current unix epoch timestamp in seconds converted into an 8-byte little-endian array. The signature is the HMAC-SHA256 digest of the payload using the secret key associated with the specified API key.
Implementation notes:
-
The signature is base-64 encoded with the 'standard' alphabet and padding.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ -
The timestamp should be encoded as 8-byte little-endian (array of bytes)
-
The secret key should be decoded from a hex string into a 32-byte array of bytes
The timestamp used for signature generation.
An error was encountered while processing the request.
The API Key ID as specified in the API settings page.
Each API key has a corresponding access level that is set when the key is created.
- Read access only allows access to read HTTP methods (GET, HEAD, etc.).
- Write access allows access to all HTTP methods.
The API signature string authenticating this request.
The payload to be signed is the concatenation of the byte string cube.xyz and the current unix epoch timestamp in seconds converted into an 8-byte little-endian array. The signature is the HMAC-SHA256 digest of the payload using the secret key associated with the specified API key.
Implementation notes:
-
The signature is base-64 encoded with the 'standard' alphabet and padding.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ -
The timestamp should be encoded as 8-byte little-endian (array of bytes)
-
The secret key should be decoded from a hex string into a 32-byte array of bytes
The timestamp used for signature generation.
Returns the most recent orders where created_at < created_before. If null, returns the most recent orders.
The maximum number of orders to return. If null, defaults to 100. The maximum is 1000.
An error was encountered while processing the request.
The API Key ID as specified in the API settings page.
Each API key has a corresponding access level that is set when the key is created.
- Read access only allows access to read HTTP methods (GET, HEAD, etc.).
- Write access allows access to all HTTP methods.
The API signature string authenticating this request.
The payload to be signed is the concatenation of the byte string cube.xyz and the current unix epoch timestamp in seconds converted into an 8-byte little-endian array. The signature is the HMAC-SHA256 digest of the payload using the secret key associated with the specified API key.
Implementation notes:
-
The signature is base-64 encoded with the 'standard' alphabet and padding.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ -
The timestamp should be encoded as 8-byte little-endian (array of bytes)
-
The secret key should be decoded from a hex string into a 32-byte array of bytes
The timestamp used for signature generation.
An error was encountered while processing the request.
The API Key ID as specified in the API settings page.
Each API key has a corresponding access level that is set when the key is created.
- Read access only allows access to read HTTP methods (GET, HEAD, etc.).
- Write access allows access to all HTTP methods.
The API signature string authenticating this request.
The payload to be signed is the concatenation of the byte string cube.xyz and the current unix epoch timestamp in seconds converted into an 8-byte little-endian array. The signature is the HMAC-SHA256 digest of the payload using the secret key associated with the specified API key.
Implementation notes:
-
The signature is base-64 encoded with the 'standard' alphabet and padding.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ -
The timestamp should be encoded as 8-byte little-endian (array of bytes)
-
The secret key should be decoded from a hex string into a 32-byte array of bytes
The timestamp used for signature generation.
An error was encountered while processing the request.
The API Key ID as specified in the API settings page.
Each API key has a corresponding access level that is set when the key is created.
- Read access only allows access to read HTTP methods (GET, HEAD, etc.).
- Write access allows access to all HTTP methods.
The API signature string authenticating this request.
The payload to be signed is the concatenation of the byte string cube.xyz and the current unix epoch timestamp in seconds converted into an 8-byte little-endian array. The signature is the HMAC-SHA256 digest of the payload using the secret key associated with the specified API key.
Implementation notes:
-
The signature is base-64 encoded with the 'standard' alphabet and padding.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ -
The timestamp should be encoded as 8-byte little-endian (array of bytes)
-
The secret key should be decoded from a hex string into a 32-byte array of bytes
The timestamp used for signature generation.
An error was encountered while processing the request.
The API Key ID as specified in the API settings page.
Each API key has a corresponding access level that is set when the key is created.
- Read access only allows access to read HTTP methods (GET, HEAD, etc.).
- Write access allows access to all HTTP methods.
The API signature string authenticating this request.
The payload to be signed is the concatenation of the byte string cube.xyz and the current unix epoch timestamp in seconds converted into an 8-byte little-endian array. The signature is the HMAC-SHA256 digest of the payload using the secret key associated with the specified API key.
Implementation notes:
-
The signature is base-64 encoded with the 'standard' alphabet and padding.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ -
The timestamp should be encoded as 8-byte little-endian (array of bytes)
-
The secret key should be decoded from a hex string into a 32-byte array of bytes
The timestamp used for signature generation.
An error was encountered while processing the request.
The API Key ID as specified in the API settings page.
Each API key has a corresponding access level that is set when the key is created.
- Read access only allows access to read HTTP methods (GET, HEAD, etc.).
- Write access allows access to all HTTP methods.
The API signature string authenticating this request.
The payload to be signed is the concatenation of the byte string cube.xyz and the current unix epoch timestamp in seconds converted into an 8-byte little-endian array. The signature is the HMAC-SHA256 digest of the payload using the secret key associated with the specified API key.
Implementation notes:
-
The signature is base-64 encoded with the 'standard' alphabet and padding.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ -
The timestamp should be encoded as 8-byte little-endian (array of bytes)
-
The secret key should be decoded from a hex string into a 32-byte array of bytes
The timestamp used for signature generation.
The subaccount to withdraw from.
The asset to withdraw. The network is determined by the asset ID.
The amount to withdraw. This is denominated in the smallest unit of the asset (e.g. satoshis for BTC, wei for ETH, lamports for SOL). The amount must be greater than the dust limit for the asset.
The destination address for the withdrawal.
Base-64 encoded cube_ov_utils::ov_schema::PublicKey
Base-64 encoded signature of this withdrawal request
An error was encountered while processing the request.
Last updated