Versioning & Lifecycle
Headers that carry version, deprecation and end-of-life. The category the catalog shows to be almost entirely unused, which is a finding rather than a gap in the data.
11 headers, ordered by how many providers in the catalog declare them.
x-v
61 providers
regulated
2 spellings
Version negotiation made binding by law in Australia.
x-min-v
61 providers
regulated
The x-min-v HTTP header — versioning & lifecycle, declared by 61 providers in the API Evangelist catalog.
api-version
29 providers
3 spellings
The api-version HTTP header — versioning & lifecycle, declared by 29 providers in the API Evangelist catalog.
X-Api-Version
28 providers
4 spellings
The X-Api-Version HTTP header — versioning & lifecycle, declared by 28 providers in the API Evangelist catalog.
Sunset
10 providers
regulated
2 spellings
When the resource goes away. Six providers in the catalog declare it.
Deprecation
7 providers
regulated
2 spellings
Declared by three providers in the entire catalog. The market's answer to "when does this endpoint die" is a blog post.
OData-Version
3 providers
The OData-Version HTTP header — versioning & lifecycle, declared by 3 providers in the API Evangelist catalog.
OData-MaxVersion
1 providers
The OData-MaxVersion HTTP header — versioning & lifecycle, declared by 1 providers in the API Evangelist catalog.
OSLC-Core-Version
The OSLC-Core-Version HTTP header — versioning & lifecycle, not observed in the catalog.
MIME-Version
The MIME-Version HTTP header — versioning & lifecycle, RFC 9112, not observed in the catalog.
Content-Version
The Content-Version HTTP header — versioning & lifecycle, RFC 2068, not observed in the catalog.