Errors
op_endpoint_sunset
410 — the endpoint has been sunset; see the Link header for the migration guide.
Last updated
Cause
Matter publishes a clear deprecation lifecycle: announce, mark deprecated, sunset. An endpoint that has progressed through deprecated state and reached sunset is permanently retired. op_endpoint_sunset fires when a caller submits a request to a retired endpoint. The response carries a Link header pointing at the migration guide and the replacement operation.
Sunsetting is announced well in advance via the changelog, customer email, and the Deprecation and Sunset headers that begin appearing on deprecated endpoints before the cutover date. Calls to a sunset endpoint do not partial-execute — the request is rejected at the routing layer before any business logic runs.
Fix
- Read the
Linkheader on the 410 response. It points at the migration guide for the specific endpoint. - Update the caller to use the replacement operation. The migration guide names the new operation and outlines any shape changes.
- Search the codebase for other callers of the same endpoint and migrate them in the same change. Sunset rarely affects a single call site.
- Subscribe to the API changelog at
/changelogso future sunsets are picked up during deprecation rather than at cutover.
Related codes
op_provider_unavailable— an external provider is unreachable, not Matter itself.op_service_degraded— temporary load-shedding, not a permanent retirement.