Changelog#

2026-09-18#

[Deprecation] Python 3.9 runtime no longer accepted for new scripts
- Scripts
The python3.9 runtime is no longer accepted when creating or updating a script. All new scripts default to python3.13. Existing scripts that use python3.9 continue to return that value in responses, and historical runs are unaffected. Note that the PATCH endpoint uses a JSONPatchDocument request body, so the runtime restriction on updates is enforced server-side rather than in the schema.

[Feature] Idempotent script execution
- Scripts
The script execution endpoint now accepts an optional X-Scripting-Nonce header. If a request with the same nonce was already processed for the script, the original run is returned instead of starting a new one.

[Information] Correct PATCH script documentation
- Scripts
Added name to the list of allowed replace operations when partially updating a script. Removed name from the required properties for script creation.
[Bug Fix] Environment variables reach script runs
- Scripts
The Script Execution endpoint now correctly forwards request body properties as environment variables to script runs. A maximum of 500 properties is allowed.

[Information] Document 204 No Content response for content download
- Scripts
The content download endpoint now documents a 204 No Content response for script sources that have no content to download.

[Feature] Initial feature preview release
Initial feature preview release of the Scripting API. Provides endpoints for managing scripts, script runs, script sources, and dependency management.
[Feature] Script permissions management
- Permissions
- Scripts
We’ve introduced dedicated endpoints for managing script permissions. You can now retrieve and modify who has access to a script programmatically, bringing scripts in line with the permissions management already available for files, documents, spreadsheets and presentations.
[Feature] Operations endpoint
- Operations
- Scripts
We’ve added an endpoint for retrieving an operation by its ID. The long-running endpoints in this API — starting a run, generating a dependency bundle, exporting and synchronizing sources, and uploading source content — return a Location header pointing at this endpoint. Poll it to follow an operation to completion, then read resourceUrl for a link to the resulting resource.