> ## Documentation Index
> Fetch the complete documentation index at: https://docs.corti.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Upcoming Changes
> Learn about deprecations and upcoming breaking changes
## Overview
As detailed in our [Changes Policy](/release-notes/change-policy), we from time to time are forced to introduce breaking changes as we evolve our API.
Similarly, we might once in a while deprecate existing functionalities when newer functionalities serve a similar purpose in a better way.
This page lists all upcoming deprecations and their potential breaking change impact details.
The update date on this page indicates the release date where we announce the deprecation. It is immediately in effect, while the shutdown (sunset) date is the date where only the new API behaviour or model is available anymore.
### Formatting Change for Medical Codes
| Property | Description |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Change | To align with standard formatting, Corti will update the API response of medical codes to include decimal points. |
| Affected endpoints | [Predict Codes](/api-reference/codes/predict-codes) |
| Impact | Medical Codes generated by the API will include decimal points. Client side formatting to add decimal points will no longer be needed. Example: A code currently returned as M751 will be returned as M75.1 |
| Change date | **May 22nd, 2026** |
### Property name changes for GET template(s), GET sections
| Property | Description |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Change | To align with our API conventions, we are changing from snake\_case to camelCase property naming. Some properties are renamed: `date_updated` -> `updatedAt`, `section_type` -> `type`, `sections_id` -> `section` |
| Affected endpoints | [List templates](/api-reference/templates/list-templates), [List template sections](/api-reference/templates/list-template-sections), [Get template](/api-reference/templates/get-template) |
| Impact | Both snake\_case and camelCase or slightly renamed properties are being returned until the shutdown date. |
| Shutdown date | **January 6th, 2026**: We will not return snake\_case properties anymore, please ensure you have adopted any necessary changes before that date. |
| Related Guide | [Retrieving available templates](/textgen/templates#retrieving-available-templates) |
### Property name change for additionalInstructions
| Property | Description |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Change | As we evolve the documents endpoint, we are renaming the `additionalInstructions` property to `additionalInstructionsOverride` for clarity that this field overrides any existing default. |
| Affected endpoints | [POST documents from dynamic template](/api-reference/documents/generate-document#dynamic-template) |
| Impact | Until shutdown, both the now deprecated `additionalInstructions` as well as the new `additionalInstructionsOverride` are accepted in the request. |
| Shutdown date | **January 6th, 2026**: We will not accept `additionalInstructions` anymore, please ensure you have adopted any necessary changes before. |
| Related Guide | [Advanced Document Generation](/textgen/documents-advanced) |
### Request schema change for POST documents template object
| Property | Description |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Change | As we evolve the documents endpoint, we are changing the request schema when assembling sections into a template at the request. We are deprecating the `sectionKeys` property of type string\[] in favour of the new `sections` property of type object\[]. The new property requires at minimum a `key` with the sectionKey as value and can be optionally extended to customize several section fields with overrides. As previously and unchanged: the sorting of sections is implicit as set by the order of keys in the array. |
| Affected endpoints | [POST documents from dynamic template](/api-reference/documents/generate-document#dynamic-template) |
| Impact | Until shutdown, both the now deprecated `sectionKeys` string\[] as well as the new `sections` object\[] can be passed in the request. |
| Shutdown date | **January 6th, 2026**: We will not accept `sectionKeys` anymore, please ensure you have adopted any necessary changes before. |
| Related Guide | [Advanced Document Generation](/textgen/documents-advanced) |