> For the complete documentation index, see [llms.txt](https://docs.unifize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unifize.com/release-notes/november-2025/update-production-api-server.md). # Update Production API server ### Introduction This release updates the Production API Server to a newer backend version focused on improving the performance and stability of Linked Record operations. The update removes unused portions of the API response that were previously generated but not required by the platform. By eliminating this unnecessary processing, the API now returns a smaller response payload and reduces the time taken to load linked fields inside a checklist. No functional behaviour has been changed as part of this update; all linked field and embedded field workflows are expected to operate exactly as before. *** ### **Release Scope** * Updated the API server to v5.15.43, which is a newer, optimised version. * Removed unused embedded-field data previously fetched from the API to get the linked field value. * Improved API response payloads for embedded fields to reduce load time. * Ensured no functional behaviour changes in how embedded fields are selected, displayed, edited, or updated. * Validated complete UI flow for: * Checklist UI with embedded fields * Linked Record field display * Embedded field visibility and ordering * Embedded field deletion and updates * Verified that checklist conditions dependent on embedded fields continue working as expected. * Confirmed performance improvement in loading embedded fields within Linked Records. *** ### **Before vs After** | Area | Before the Update | After the Update | | -------------------------- | --------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | | **API Behaviour** | API returned additional unused details while fetching embedded field values. | API returns only required data → lighter payload and faster processing. | | **Embedded Field Loading** | Slower loading time, especially for Linked Records with multiple embedded fields. | Noticeably improved loading speed for embedded fields. | | **Checklist UI Behaviour** | Fully functional but dependent on heavier database queries. | Functional behaviour unchanged, but with optimised backend queries. | | **Ordering & Visibility** | Reordering and visibility changes worked but were slower to reflect. | Reordering, visibility, and deletion flow remain the same but respond faster. | *** For more details about Unifize APIs, check out the complete [API documentation here](https://docs.unifize.com/developer/introduction). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.unifize.com/release-notes/november-2025/update-production-api-server.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.