# Versioning and deprecations

> How DigitSpace changes its API - what may change without notice, the 90 days' notice before anything is removed, and how models are retired.

Source: https://digitspace.ai/docs/reference/versioning · Last checked: 2026-10-31

The gateway API is version 1, under `/v1`. Its formats follow OpenAI's Chat Completions and Anthropic's Messages.

## What can change without notice

Changes that don't break code written against the documented API:

- new endpoints, fields, headers, error codes and models;
- new optional request fields;
- new values in fields that list things, such as `providers`;
- error messages (match on `type` and `code` instead);
- which provider serves a request, unless you pin one.

Write code that ignores fields it doesn't know.

## What gets 90 days' notice

Removing or changing anything documented here that working code may rely on: an endpoint, a request or response field, a header, an error's `type` or `code`, or the meaning of a value. We announce it by email to organisation owners and admins and on this page at least 90 days before it takes effect.

Security fixes are the exception: if a behaviour puts customers at risk, we change it at once and tell you afterwards.

## Models

Models come and go with their providers. When a model is going to be retired, the dashboard's alerts (**Model retirements**) warn up to 30 days ahead, when the provider gives us that much notice. After that, requests for it return `404 model_not_found`. With `auto`, retired models simply stop being chosen.

## Changes

| Date       | Change                |
| ---------- | --------------------- |
| 2026-10-31 | These docs published. |