SaSameFor people and AI systems
Search knowledgeExplore markets
Historical record · Not current

Preserved for provenance and historical reference. This record does not describe a current product, service, price, or operating model.

historicalarchivearchive

How should deprecated SaSame APIs be handled?

The record prevents silent interface removal and gives machine clients a bounded transition path.

Collection
archive
Updated
2026-07-30
min read
2
Verified summary

Deprecated APIs remain documented for migration with replacement endpoints, sunset state and compatibility limits.

01

Purpose

The record prevents silent interface removal and gives machine clients a bounded transition path.

02

Method

Deprecated schemas and examples remain versioned and outside current primary navigation.

03

Boundary and limitations

Deprecated does not mean supported indefinitely, and archived examples are not current authentication guidance.

EX

Examples

2
  1. 01

    A retired endpoint remains in Archive with a link to the Knowledge API replacing it.

  2. 02

    A client still calling a sunset endpoint sees a clear replacement path in this record rather than a silent 404.

RF

References

1
NX

Continue exploring

3
archive01

Mission Archive

Historical products, architectures, pricing and research are preserved for provenance in a separate, explicitly non-current collection.

api02

API

Use the read-only Knowledge API, search endpoint or MCP retrieval tools, all backed by the same document and relation model.

documentation03

Reference

Reference pages expose versioned schemas, status enums, API contracts, evidence boundaries and release receipt fields used across human and machine interfaces.