Skip to main content
GET
/
changelog
API version history with breaking-change flags
curl --request GET \
  --url https://api.example.com/changelog \
  --header 'X-API-Key: <api-key>'
{
  "data": {
    "current_version": "<string>",
    "releases": [
      {
        "version": "<string>",
        "released_at": "<string>",
        "summary": "<string>",
        "breaking": false,
        "changes": []
      }
    ],
    "docs_url": "/v2/docs",
    "openapi_url": "/v2/openapi.json"
  },
  "meta": {
    "version": "<string>",
    "timestamp": "<string>",
    "request_id": "<string>",
    "symbol": "<string>",
    "spot_price": 123,
    "computed_at": "<string>",
    "freshness_seconds": 123,
    "source": [
      "<string>"
    ],
    "exchanges_filtered": [
      "<string>"
    ],
    "rate_limit": {},
    "extra": {}
  },
  "success": true
}

Documentation Index

Fetch the complete documentation index at: https://docs.backquant.com/llms.txt

Use this file to discover all available pages before exploring further.

Static release log with per-version breaking flags. Customers integrating against the API use this to decide when to schedule re-integration work - breaking: true on any release is the signal to test.

Authorizations

​
X-API-Key
string
header
required

Your BackQuant API key (same key as v1)

Headers

​
X-API-Key
string | null

Response

Successful Response

​
data
ChangelogData · object
required
​
meta
V2Meta · object
required

The meta block returned alongside every v2 response.

Every field after version/timestamp is optional because endpoints attach different combinations — e.g. /v2/status skips symbol, the chain endpoint sets extra.filter_hash, etc. Listing them here means SDKs get a typed accessor for each instead of a generic meta: dict.

​
success
boolean
default:true