# Get supported API versions Returns a list of supported API versions with their deprecation status. Use this endpoint to discover available versions and plan migrations when versions are deprecated. Endpoint: GET /api/v1/versions Version: v1.0.3 ## Response 200 fields (application/json): - `supported_versions` (array, required) List of all supported API versions. - `supported_versions.version` (string, required) The version identifier to use in the X-Truex-Version header. Example: "v2024_01_01" - `supported_versions.deprecated` (boolean, required) Whether this version is deprecated and scheduled for removal. - `supported_versions.deprecation_date` (string) HTTP-date format timestamp of when the version was deprecated. Only present if deprecated is true. Example: "Sat, 01 Feb 2025 00:00:00 GMT" - `supported_versions.sunset_date` (string) HTTP-date format timestamp of when the version will be removed. Only present if deprecated is true. Example: "Sun, 01 Feb 2026 00:00:00 GMT" - `default_version` (string, required) The version used when no X-Truex-Version header is provided. Example: "v2024_01_01" - `version_header` (string, required) The header name to use for specifying API version. Example: "X-Truex-Version" ## Response 400 fields (application/problem+json): - `type` (string, required) A URI reference that identifies the problem type. Example: "about:blank" - `title` (string, required) A short, human-readable summary of the problem type. Example: "An Error Occured" - `status` (integer, required) The HTTP status code generated by the origin server. Example: 400 - `detail` (string) A human-readable explanation specific to this occurrence of the problem. Example: "A more detailed sentence about the error" - `instance` (string) A URI reference that identifies the specific occurrence of the problem. Example: "/api/v1/endpoint" - `extensions` (object) A map for extension members (custom fields not defined by the RFC).