tastytradeDeveloper Docs
Legacy ↗

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 20250830 is live. The header is matched against versions that currently exist, not to the nearest one.

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.

New versions and deprecations are announced in Release notes. If you pin a version, watch that page and move forward before your pinned version's window closes — otherwise the first sign of trouble is a 406 in production.

Finding the available versions

Each reference page states which versions are available and which are deprecated. Pages with more than one version show a dropdown at the top for viewing each:

The API version dropdown shown at the top of a multi-version reference page

Older versions will contain one or more deprecated endpoints.

Related