--- title: "8.0.0 Platform Release Notes" slug: "8-0-0-platform-release-notes" status: "update" updated: 2026-09-24T13:45:14Z published: 2026-09-24T13:45:14Z canonical: "docs.unqork.io/8-0-0-platform-release-notes" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.unqork.io/llms.txt > Use this file to discover all available pages before exploring further. # 8.0.0 Platform Release Notes **Released**: March 10, 2026 **Type**: Major Release ## Release Schedule Announcement Starting with version 8.0, Unqork is moving to a quarterly General Availability (GA) release calendar. This new 12-week cycle replaces the previous 6-week model, giving teams more predictability and time to adopt new capabilities. Critical patch releases continue to deploy weekly. ## Improvements ### Administration - **Services Administration**: Unqork has enhanced the reliability of external service integrations using the Enable Token Persistence feature by implementing strict, real-time expiration checks. Previously, tokens were validated only at the start of a request, which could result in expired tokens being used mid-request. Tokens are now revalidated immediately before each service call. - **Environment Administration**: Fixed inaccurate helper text in Environment Administration. ### APIs As part of Unqork's ongoing migration from GraphQL endpoints to REST endpoints, this release includes the following updates: - Implemented a high-performance REST `/records/:recordId` endpoint for retrieving Data Model, module, and workflow records — a faster alternative to the legacy GraphQL `getRecord` resolver. - Implemented a new REST `getSearchConfig` endpoint to support search service replacements with the ADS package. - Implemented a new REST `getRecordsCount` endpoint for modules, workflows, and data models. - Implemented a new REST `getRecords` endpoint. - Implemented a new REST `restoreSchema` endpoint. - Implemented a new REST `getSchemas` endpoint. - Implemented a new REST `getModulesByModels` endpoint. - Implemented a new REST `getModelsFromSchema` endpoint. - Implemented a new REST `POST /schemas/data-validation` endpoint. The former GraphQL `POST /models/validateFromSchema` endpoint is marked as deprecated but continues to be supported until no active usage remains. - **API Documentation**: Updated the Update User (`PUT /users/{userId}`) documentation to clarify that the `userId` field cannot be modified, and that the `shouldNotify` parameter enables the New Account email only and does not suppress User Changed notifications. > [!NOTE] > The `/fbu/uapi/pdfbar/combine` `flatten` parameter is scheduled for removal in version 8.2.0. The `/fbu/uapi/image/parsePDF` endpoint is also scheduled for removal in version 8.2.0. ### Application Versioning - **Service Logs**: Service logs now contain information about the context of the origin request to improve debugging capabilities. ### Module Builder - **Dynamic Grid component**: Column triggers and display behavior have been stabilized for this release. ### Data - Unqork has expanded REST endpoint coverage for Data Models and schema operations, replacing legacy GraphQL . ## Security This release includes scheduled security patches. No action is required. --- **Changelog** | Date | Change | | --- | --- | | 2026-09-14 | Initial publication (EN-8111). | A functionality of a software. For example, Copy and Paste is a feature of a computer's operating system. An API endpoint is the location where an API receives requests for a specific resource on its server. It's the point of contact between an API client and an API server, and is usually a uniform resource locator (URL) that provides the location of the resource. The REST (representational state transfer) API is a set of architectural constraints used to exchange information securely over the internet. An API endpoint is the location where an API receives requests for a specific resource on its server. It's the point of contact between an API client and an API server, and is usually a uniform resource locator (URL) that provides the location of the resource. GraphQL resolvers let define how you want to populate data, likefetching data from a database or a third-party API. Schema is a declarative language that defines the structure, content, and constraints of the data.