API Key Behavior Updates
FastGPT 4.15.00 modifies API key handling by eliminating separate app key authentication, retaining only system keys for all access. To maintain compatibility with OpenAI SDKs, authenticate requests using a token formatted as apikey-appId instead of the standalone API key used previously. All existing API keys will remain fully compatible and continue to operate without immediate modification. For complete implementation guidelines, refer to the official FastGPT API documentation.
Stricter API Data Validation
Multiple core FastGPT APIs now enforce more rigorous data format validation against their declared schemas. If you encounter a zod parse error during API interactions, submit a detailed issue report. This error typically arises from legacy stored data or custom data structures that no longer align with the updated schema requirements.
LLM Request Trace Changes & Required Index Sync
This update introduces team isolation for all LLM request trace data, with three key structural modifications:
- The
llm_request_recordsdatabase table now includes ateamIdfield for every trace entry - The
GET /api/core/ai/record/getRecordendpoint now requires bothrequestIdandteamIdquery parameters to retrieve trace data - The table's unique index is updated from a single
requestIdfield to the composite{ teamId, requestId }index
Pre-upgrade trace records do not contain a teamId value, so they cannot be queried via the updated endpoint and will be marked as expired in the FastGPT UI. If you need to investigate historical LLM calls, export relevant logs or preserve original request details prior to completing the upgrade.
For self-hosted deployments where SYNC_INDEX is disabled, complete this mandatory step after upgrading:
- Connect to your FastGPT database instance
- Run the database index synchronization process to remove the legacy
requestId_1unique index - Confirm the new composite
{ teamId, requestId }index is active in the database