እኛ የጣቢያ ትንተና ለማካሄድ እና ፈቅደው ካስቀመጡት ለግል ያልተመረጠ ማስታወቂያ ለማሳየት ኩኪዎችን እንጠቀማለን። እነዚህ ሁለት የተለያዩ ምርጫዎች ናቸው፤ ጣቢያውን ለመጠቀም ሁለቱም አስፈላጊ አይደሉም።የትንተናና የማስታወቂያ ኩኪዎች አማራጭና የተለያዩ ናቸው። የግላዊነት ፖሊሲ
አሁን ተገቢ ተመን የለም
This document describes how the exchange.et API is versioned and how endpoints are deprecated and eventually removed. It is deliberately split into two parts: what is true today (factual, verifiable) and the forward-looking policy (commitments we intend to honour, none of which have been exercised yet).
/api/v1 (basePath: /api/v1; the OpenAPI info.version reports 1.0.0)./healthz is marked deprecated: true in the public OpenAPI spec in favour of the canonical /health endpoint (same view, same contract). It is still served and has no Deprecation/Sunset response headers and no removal date.In short: the policy below is forward-looking. Nothing described here has fired yet because there is nothing to deprecate beyond the /healthz alias annotation.
/api/v1/.... A breaking change lands under a new major path (e.g. /api/v2/...), never silently inside v1.v1 remains available until its deprecation + sunset cycle below has completed.info.version (1.0.0) is a release marker, not the versioning contract; the URL prefix (/api/v1) is the contract consumers pin to.When an endpoint (or a specific field/parameter) is scheduled for removal, we will, before removing it:
/developers) and in the API reference (/docs).Deprecation: @1796115600
Deprecation (RFC 9745) is a Structured Field date — the number of seconds since the Unix epoch, prefixed with @ — marking when the endpoint will be removed (the sunset date). If a replacement exists, a Link header with rel="deprecation" (or rel="successor-version") points at it.Sunset: Tue, 01 Dec 2026 12:00:00 GMT
deprecated: true in the OpenAPI spec, with the removal date and replacement noted in its description.These headers are the machine-readable commitment: a client can detect a deprecation from the response without reading any changelog.
Deprecation header) to removal. During that window the endpoint keeps its current behaviour and response shape.Deprecation/Sunset headers from day one, so the window is never shortened silently.404/410 (Gone) rather than a silently changed response./api/v1/...), not to a bare host path.Deprecation and Sunset response headers as actionable: when you see them, migrate before the advertised date.This page is the canonical record of the policy. The developer portal (/developers) carries a short summary; if the two ever diverge, this document is authoritative.