Version¶
Inspect the deployed Tango API version and build date. Useful for logging, support tickets, and client-side feature detection.
Endpoint¶
GET /api/version/
No authentication required.
Response¶
| Field | Type | Description |
|---|---|---|
version | string | Semantic version string (e.g. 4.4.0). Bumped on each release per Keep a Changelog conventions; see the public Changelog. |
date | string | RFC 2822 build / release date (e.g. "Mon, 08 May 2026 12:17:42 GMT"). |
{
"version": "4.4.0",
"date": "Mon, 08 May 2026 12:17:42 GMT"
}
Example¶
curl -sS https://tango.makegov.com/api/version/
When to use¶
- Bug reports: include the live
versionvalue alongside the request that failed; it speeds up triage. - Client compatibility: an SDK can refuse to start (or warn) when the API is older than its minimum supported version.
- Cache invalidation: a version bump is a good signal to invalidate any client-side cached schemas (e.g. response-shape help retrieved via
?show_shapes=true).