tastytradetastytrade

API Versions

tastytrade sometimes needs to introduce breaking changes to an endpoint. Rather than change it under you, the existing version is deprecated and the breaking change goes into a new API version.

Versions are dates

A version is always the date it was introduced, as YYYYMMDD. A version introduced on 4 September 2025 is 20250904.

To target one, send the Accept-Version header on each request:

GET /accounts HTTP/1.1
Host: api.tastyworks.com
Authorization: Bearer <access token>
User-Agent: my-custom-client/1.0
Accept-Version: 20250904

Requesting a version that no longer exists

You get an HTTP 406:

{
  "error": {
    "code": 406,
    "message": "The requested version is not supported."
  }
}

For example, targeting 20240829 once it has been removed returns the above, even though later versions exist.

In order-api, a header that falls between two existing versions is served the highest existing version at or below it. With 20250813 and 20261012 both live, 20260101 is served 20250813. Only a header older than every existing version gets the 406.

Deprecation window

When a new version is introduced, older versions are deprecated. A deprecated version has at least 6 months to live from the point of deprecation.

If you pin a version, plan to move forward before its window closes — otherwise the first sign of trouble is a 406 in production.

Finding the available versions

The API Reference has no version selector, and its pages do not state which version they describe, so don't read a page as confirmation that a given Accept-Version value is still accepted.

Deprecation is only partly visible in the reference. The OpenAPI files carry a deprecated flag on some operations, but the reference pages do not display it. A page shows a deprecation only where the endpoint's description says so in words. GET /instruments/future-option-products/{root_symbol} is an example of both: the operation carries the flag and its description says so.

Release notes lists notable API changes under date headings, newest first. It is not a complete list of versions, and it has no deprecation notice for each deprecated endpoint, so don't rely on it alone to know which version or endpoint is deprecated.

Related