tastytradeDeveloper Docs
Legacy ↗

API Reference / Net Liquidating Value History

Get Net-Liq History For Account

getNetLiqHistory
get/accounts/{accountNumber}/net-liq/history

Base URL: https://api.cert.tastyworks.com (Sandbox) · https://api.tastyworks.com (Production)

Returns the account's net liquidating value history (the total current value of the account — roughly the cash you would end up with if you closed every position) as open/high/low/close data. Use the `time-back` parameter for a window relative to now (`1d`, `1w`, `1m`, `3m`, `6m`, `1y`, `all`), or supply `start-time`/`end-time` for an explicit window. This is a read-only endpoint and moves no money.

Code samples

curl -X GET 'https://api.cert.tastyworks.com/accounts/{accountNumber}/net-liq/history?time-back=1d&start-time=%7Bstart-time%7D&end-time=%7Bend-time%7D&interval=%7Binterval%7D' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  -H 'User-Agent: tastytrade-docs-example/1.0'

Parameters

NameInTypeDescription
accountNumber*pathstring
time-backquerystringA request of data relative to the current time
enum: 1d, 1w, 1m, 3m, 6m, 1y, all
e.g. "1d"
start-timequerystringThe start-time of a windowed request in format '2011-12-03T10:15:30+01:00[Europe/Paris]'
end-timequerystringThe end-time of a windowed request in format '2011-12-03T10:15:30+01:00[Europe/Paris]'
intervalquerystring

Responses

200Net-liq history for the account over the requested window, as open/high/low/close data.*/*

Example response

{
  "data": {
    "open": 32100.5,
    "high": 32650.75,
    "low": 31980.25,
    "close": 32520.734,
    "totalOpen": 32100.5,
    "totalHigh": 32650.75,
    "totalLow": 31980.25,
    "totalClose": 32520.734,
    "pendingCashOpen": 0,
    "pendingCashHigh": 0,
    "pendingCashLow": 0,
    "pendingCashClose": 0,
    "time": "string"
  },
  "context": "/accounts/{accountNumber}/net-liq/history"
}

Schema

  • datarequiredobject (NetLiqOhlc)

    A single open/high/low/close record of an account's net liquidating value over an interval. The `open`/`high`/`low`/`close` fields track the account's net liquidating value, and the `pendingCash*` fields track cash that is temporarily in a holding period while a cash transfer is processed.

    • opennumber <double>

      Net liquidating value at the start of the interval.

      example: 32100.5

    • highnumber <double>

      Highest net liquidating value observed during the interval.

      example: 32650.75

    • lownumber <double>

      Lowest net liquidating value observed during the interval.

      example: 31980.25

    • closenumber <double>

      Net liquidating value at the end of the interval.

      example: 32520.734

    • totalOpennumber <double>

      Total net liquidating value at the start of the interval.

      example: 32100.5

    • totalHighnumber <double>

      Highest total net liquidating value observed during the interval.

      example: 32650.75

    • totalLownumber <double>

      Lowest total net liquidating value observed during the interval.

      example: 31980.25

    • totalClosenumber <double>

      Total net liquidating value at the end of the interval.

      example: 32520.734

    • pendingCashOpennumber <double>

      Pending cash (cash mid-transfer that has not cleared) at the start of the interval. Usually 0.

      example: 0

    • pendingCashHighnumber <double>

      Highest pending cash observed during the interval. Usually 0.

      example: 0

    • pendingCashLownumber <double>

      Lowest pending cash observed during the interval. Usually 0.

      example: 0

    • pendingCashClosenumber <double>

      Pending cash at the end of the interval. Usually 0.

      example: 0

    • timestring

      Timestamp marking the record within the requested window.

  • contextrequiredstring

    example: "/accounts/{accountNumber}/net-liq/history"

401Missing or invalid authentication. Send a valid `Authorization: Bearer <token>` (access tokens last 15 minutes) and always include a `User-Agent` header in the form `<product>/<version>`.application/json

Example response

{
  "error": {
    "code": "unauthorized",
    "message": "No valid access token was provided; access tokens expire after 15 minutes."
  }
}

Schema

  • errorrequiredobject
    • coderequiredstring

      Machine-readable error code (see the Error reference).

    • messagerequiredstring

      Human-readable explanation.

    • errorsarray<object>{3 fields}

      Present for multi-error / validation failures; one entry per problem.

403Authenticated, but the token's scope or the account's authority level does not permit reading this account's net-liq history.application/json

Example response

{
  "error": {
    "code": "not_permitted",
    "message": "User not permitted access"
  }
}

Schema

  • errorrequiredobject
    • coderequiredstring

      Machine-readable error code (see the Error reference).

    • messagerequiredstring

      Human-readable explanation.

    • errorsarray<object>{3 fields}

      Present for multi-error / validation failures; one entry per problem.

404No account matches the supplied `accountNumber`, or the request was sent to the wrong environment (sandbox `api.cert.tastyworks.com` vs production `api.tastyworks.com`).application/json

Example response

{
  "error": {
    "code": "string",
    "message": "string",
    "errors": [
      {
        "code": "string",
        "message": "string",
        "domain": "string"
      }
    ]
  }
}

Schema

  • errorrequiredobject
    • coderequiredstring

      Machine-readable error code (see the Error reference).

    • messagerequiredstring

      Human-readable explanation.

    • errorsarray<object>{3 fields}

      Present for multi-error / validation failures; one entry per problem.

429Request rate exceeded reasonable thresholds. Back off exponentially and reduce your request rate before retrying.application/json

Example response

{
  "error": {
    "code": "string",
    "message": "string",
    "errors": [
      {
        "code": "string",
        "message": "string",
        "domain": "string"
      }
    ]
  }
}

Schema

  • errorrequiredobject
    • coderequiredstring

      Machine-readable error code (see the Error reference).

    • messagerequiredstring

      Human-readable explanation.

    • errorsarray<object>{3 fields}

      Present for multi-error / validation failures; one entry per problem.

Related

Agents: this page is also Markdown (with the embedded OpenAPI definition) — append .md or send Accept: text/markdown. Index at /llms.txt.