# Get orders (deprecated) (deprecated)

 Fetches all orders for a client entered within the past 24 hours on the exchange. A filter can be provided to limit the results.

Endpoint: GET /api/v1/order
Version: v1.0.3
Security: HMAC

## Header parameters:

  - `x-truex-auth-userid` (string, required)
    Client identifier.

  - `x-truex-auth-timestamp` (string, required)
    Timestamp when request was made in seconds since epoch.

  - `x-truex-auth-token` (string, required)
    The UUID affiliated with the HMAC key.

  - `x-truex-auth-signature` (string, required)
    The computed HMAC signature.

## Query parameters:

  - `size` (string)
    Number of records to return per page. Maximum allowed value is 100.

  - `skip` (string)
    Number of records to skip before returning results. Used for offset-based pagination.

  - `timestamp` (string, required)
    A Unix UTC timestamp in nanoseconds used as a reference point for fetching orders. The query will retrieve results created  this timestamp, enabling precise time-based filtering and ensuring stable pagination. If omitted, the server responds with .
    Example: "1741523275598727336"

## Response 200 fields (application/json):

  - `client_id` (string)
    A unique identifier assigned to the client.
    Example: "78901968715907076"

  - `instrument_id` (string)
    A unique identifier for the trading instrument.
    Example: "78901968728948750"

  - `order_id` (string)
    A unique identifier for the order.
    Example: "8005237327190949926"

  - `trade_price` (string)
    The price at which the trade was executed.
    Example: "111480.5"

  - `trade_qty` (string)
    The quantity of the asset traded.
    Example: "0.06089"

  - `trade_fee_rate` (string)
    The fee rate applied to the trade.
    Example: "0.0005"

  - `liq_flag` (string)
    Indicates whether the trade was executed as a taker or a maker.
    Enum: "TAKER", "MAKER"

  - `match_id` (string)
    A unique identifier for the trade match event.
    Example: "147670564223998146302870408890920992792"

  - `timestamp` (string)
    The Unix UTC timestamp (in nanoseconds) when the trade was executed.
    Example: "1752163579133484200"

## Response 400 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type.
    Example: "about:blank"

  - `title` (string, required)
    A short, human-readable summary of the problem type.
    Example: "An Error Occured"

  - `status` (integer, required)
    The HTTP status code generated by the origin server.
    Example: 400

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "A more detailed sentence about the error"

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem.
    Example: "/api/v1/endpoint"

  - `extensions` (object)
    A map for extension members (custom fields not defined by the RFC).

## Response 401 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type.
    Example: "about:blank"

  - `title` (string, required)
    A short, human-readable summary of the problem type.
    Example: "An Error Occured"

  - `status` (integer, required)
    The HTTP status code generated by the origin server.
    Example: 400

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "A more detailed sentence about the error"

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem.
    Example: "/api/v1/endpoint"

  - `extensions` (object)
    A map for extension members (custom fields not defined by the RFC).

## Response 403 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type.
    Example: "about:blank"

  - `title` (string, required)
    A short, human-readable summary of the problem type.
    Example: "An Error Occured"

  - `status` (integer, required)
    The HTTP status code generated by the origin server.
    Example: 400

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "A more detailed sentence about the error"

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem.
    Example: "/api/v1/endpoint"

  - `extensions` (object)
    A map for extension members (custom fields not defined by the RFC).

## Response 408 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type.
    Example: "about:blank"

  - `title` (string, required)
    A short, human-readable summary of the problem type.
    Example: "An Error Occured"

  - `status` (integer, required)
    The HTTP status code generated by the origin server.
    Example: 400

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "A more detailed sentence about the error"

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem.
    Example: "/api/v1/endpoint"

  - `extensions` (object)
    A map for extension members (custom fields not defined by the RFC).

## Response 415 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type.
    Example: "about:blank"

  - `title` (string, required)
    A short, human-readable summary of the problem type.
    Example: "An Error Occured"

  - `status` (integer, required)
    The HTTP status code generated by the origin server.
    Example: 400

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "A more detailed sentence about the error"

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem.
    Example: "/api/v1/endpoint"

  - `extensions` (object)
    A map for extension members (custom fields not defined by the RFC).

## Response 500 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type.
    Example: "about:blank"

  - `title` (string, required)
    A short, human-readable summary of the problem type.
    Example: "An Error Occured"

  - `status` (integer, required)
    The HTTP status code generated by the origin server.
    Example: 400

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "A more detailed sentence about the error"

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem.
    Example: "/api/v1/endpoint"

  - `extensions` (object)
    A map for extension members (custom fields not defined by the RFC).

## Response 503 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type.
    Example: "about:blank"

  - `title` (string, required)
    A short, human-readable summary of the problem type.
    Example: "An Error Occured"

  - `status` (integer, required)
    The HTTP status code generated by the origin server.
    Example: 400

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "A more detailed sentence about the error"

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem.
    Example: "/api/v1/endpoint"

  - `extensions` (object)
    A map for extension members (custom fields not defined by the RFC).