Breaking change: /api/taxiql content-type and removal of /api/vyneql

As part of upcoming feature work for improved SDK tooling for JVM and TS/JS ecosystems, there are two breaking changes to the query API are shipping in 0.38.x (and nightly builds of next). Neither affects 0.37.x.

​

Breaking: /api/taxiql no longer accepts application/json

The /api/taxiql streaming query endpoint previously accepted requests with Content-Type: application/json. This is no longer supported.

Use either of the following content types instead:

• application/taxiql (Preferred, but less standard)
• text/plain (Standard, but less accurate)

Either are fine to use, and both content types are already supported in all versions of Orbital today, so you can make this change now, without waiting.

If you’re sending queries via curl or an HTTP client, update accordingly:

# Before (no longer works)
curl -X POST /api/taxiql \
  -H "Content-Type: application/json" \
  -d '{ "query": "find { ... }" }'

# After
curl -X POST /api/taxiql \
  -H "Content-Type: application/taxiql" \
  --data-raw 'find { ... }'

​

Removal of /api/vyneql

The legacy /api/vyneql endpoint has been removed. It was a holdover from the previous product name and has been superseded by /api/taxiql for some time. If you were still referencing /api/vyneql, update your calls to use /api/taxiql.