Stability of the API
Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.
What an app can rely on as the API changes. The operations themselves are in the OpenAPI document of the instance.
From the v0 release, /api/v1 keeps these promises:
- Additions are not breaking: new fields, operations, scopes, and enum values can appear at any time. Ignore what you do not know.
- Breaking changes are announced first. Removing or renaming something, changing a type, making a field required, or changing the meaning of a scope is allowed in v0,
but the operation is first marked
deprecated: truein the OpenAPI document and its responses carry aDeprecationheader (RFC 9745, a date such as@1688169599) and aSunsetheader (RFC 8594). It stays for at least one v0.x minor release. The release notes have an “API changes” section. Log these headers in your client. - Security fixes can change behaviour without notice.
- Version 1.0 makes no breaking change to
/api/v1; one would go to/api/v2.
The OpenAPI document of the running server is at GET /api/v1/openapi.yaml, with the scopes of each operation; generate your client from it.
Detecting features
Section titled “Detecting features”An app keeps meeting servers older or newer than itself, and servers that have parts of the API off. Do not compare
version to decide what a server can do: read features of GET /api/v1/instance, a list of identifiers such as
voice_rooms or full_text_search, and offer a feature only while its identifier is listed. The OpenAPI document
says what each identifier means.
- An identifier is listed only while the feature is on, so read the list again when you refresh the instance information.
- Ignore the identifiers you do not know: new ones appear as the server gains features.
- An identifier is never removed from the API or reused for something else while
/api/v1lasts.
Für LLMs und Coding-Agenten:llms.txt,llms-full.txt, llms-small.txt