English documentation — We currently provide our documentation only in English. This helps us keep the information as accurate and up-to-date as possible during the rapid development of the API.
API
Changelog
Public API changes, additions, and deprecations.
This page lists user-visible changes to the EU GPT public API. Internal changes — model upgrades behind auto, infrastructure moves, performance improvements — are not listed here unless they affect the wire contract.
Versioning policy#
- The current major version is v1, served at
/v1/.... Breaking changes will land on a new major prefix (/v2/...). - New optional request fields and new streaming event types may land at any time. Clients should ignore unknown event types and continue to send only documented fields.
- New response fields may land at any time. Clients should ignore unknown fields.
- Deprecations announce themselves here with at least 90 days’ notice before removal.
2026-06#
max_output_tokens(optional) onPOST /v1/responses— cap the number of tokens generated for a response. Values above the selected model’s maximum are clamped. Additive; omitting it preserves the previous behaviour.
2026-05#
- Initial public release.
POST /v1/responsesis generally available with streaming and non-streaming modes. OpenAPI 3.1 spec published at/openapi.json. - Auto-approved tools for API callers:
web_search,web_fetch,calculator,current_datetime. - API key authentication via
Authorization: Bearer eugpt_<token>. Keys are managed in the web UI.
Upcoming#
Items below are committed to the roadmap but do not have firm dates. Subscribe to the changelog feed (forthcoming) for announcements.
POST /v1/files— multipart file upload to mint afile_idfrom a script.GET /v1/conversations— list, fetch, and delete conversations programmatically.- Custom tools via a per-request
tools[]parameter mirroring the Chat Completions shape. - Audio transcription at
POST /v1/audio/transcriptions, OpenAI-compatible.
Deprecations#
None yet.