# Premiere 27.0 API Updates

**URL:** <https://forums.creativeclouddeveloper.com/t/premiere-27-0-api-updates/12436>\
**Category:** Premiere Pro\
**Tags:** uxp, javascript, announcements\
**Created:** [November 12, 2026, 4:01pm UTC](https://forums.creativeclouddeveloper.com/t/premiere-27-0-api-updates/12436 "2026-11-12T16:01:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![clegleiter](https://avatars.discourse-cdn.com/v4/letter/c/3d9bf3/32.png) [@clegleiter](https://forums.creativeclouddeveloper.com/u/clegleiter)\
**Post date:** [November 12, 2026, 4:01pm UTC](https://forums.creativeclouddeveloper.com/t/premiere-27-0-api-updates/12436/1 "2026-11-12T16:01:48Z")

</div>

Hi all,

This major release of Premiere 27.0 comes with a breaking change, added features, bug fixes, and general documentation updates. As always you can also read this on the [Premiere Changelog page](https://developer.adobe.com/premiere-pro/uxp/changelog) and our updated [API doc pages](https://developer.adobe.com/premiere-pro/uxp/ppro-reference).

### UXP Updates

As part of this release Premiere has upgraded to UXP 9.4. For more details on what this includes check out the [UXP 9.4 Changelog](https://developer.adobe.com/uxp/uxp-api/changelog#uxp-v94) at the [UXP Developer Hub](https://developer.adobe.com/uxp/).

### Breaking Changes

#### The `Application` class

We’ve decided to remove the `Application` class from the exposed set of classes available from the `premierepro` module, and the `version` _asynchronous_ instance property it had documented.

```ts
const ppro = require("premierepro");
console.log(typeof ppro.Application); // "undefined"

```

The `version` property didn’t have a great way to be accessed at runtime: since there isn’t a way to properly instantiate an `Application` object to even access the `version` property, this didn’t make sense to have available in the first place. Current version information is better served through the [UXP `host` object](https://developer.adobe.com/premiere-pro/uxp/uxp-api/reference-js/modules/uxp/host-information/host) which includes _synchronous_ properties about the current Premiere version details instead, and is more consistent with other Adobe applications which support UXP plugins.

The documented `Application` class and its TypeScript declaration in `@adobe/premierepro` still remains, however, as the class is used with some `EventManager` event listener functions. We’re planning on improving our documentation generally around events and where the `Application` class does fit in here. Stay tuned!

### New APIs

A number of new classes and APIs have been added in this release. More details on each can be seen in each class’s documentation page. If you’d like to see more examples of using all of these new APIs in action, check out the `premiere-api` sample panel in the [UXP Premiere Pro Samples](https://github.com/AdobeDocs/uxp-premiere-pro-samples) repository.

- The [`Constants`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/constants/index) module has a few updates to available enumerations:

- Two new classes have been added to introduce some initial support for After Effects-authored MoGRTs when working with [`ComponentParam`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/componentparam)s:

- [`TickTime`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/ticktime) now has utility functions [`timeToTimecode`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/ticktime#timetotimecode) and [`timecodeToTime`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/ticktime#timecodetotime) for converting to and from timecode strings.

- [`TimeDisplay`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/timedisplay) now has a proper constructor to help when using with the above-added timecode utility functions. You can use the available [`Constants.AudioDisplayFormatType`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/constants/index#audiodisplayformattype) and [`Constants.VideoDisplayFormatType`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/constants/index#videodisplayformattype) with a `TimeDisplay`’s [`type`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/timedisplay#properties) property.

#### UXP Host Additions

A new property `buildNumber` has been added to the [UXP `host` object](https://developer.adobe.com/premiere-pro/uxp/uxp-api/reference-js/modules/uxp/host-information/host). This can be particularly useful for helping report any issues as of a particular version + build of Premiere.

```ts
const uxp = require("uxp");
console.log(uxp.host.version); // "27.0.0"
console.log(uxp.host.buildNumber); // "42"

```

### API Updates

- [`EventManager`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/eventmanager)’s [`removeEventListener`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/eventmanager#removeeventlistener) and [`removeGlobalEventListener`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/eventmanager#removeglobaleventlistener) functions now accept a third (optional) parameter `useCapture` matching the equivalent parameter for [`addEventListener`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/eventmanager#addeventlistener) and [`addGlobalEventListener`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/eventmanager#addglobaleventlistener). This helps make sure that adding an event listener on the capture phase can be correctly removed from the capture phase to avoid event listeners staying beyond their welcome.

- `ComponentParam`’s [`createKeyframe()`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/componentparam#createkeyframe) and [`getStartValue()`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/componentparam#createkeyframe) functions have been updated to work with the newly added `MogrtComment` and `MogrtText` classes.

### Bug Fixes

- Calling [`Exporter.exportSequenceFrame`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/exporter#exportsequenceframe) will now correctly queue calls internally. This previously caused issues when calling `exportSequenceFrame` back-to-back for multiple frames.
- [`ComponentParam.getStartValue`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/componentparam#getstartvalue) for `Color`-based `ComponentParam` should no longer be lossy. Previously there were issues maintaining the blue channel that have been resolved.
- [`SourceMonitor.openFilePath`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/sourcemonitor#openfilepath) will correctly resolve with `false` if the given file cannot be previewed in the Source Monitor.

### Documentation Updates

Outside of the above core changes, we’ve also updated our documentation and `@adobe/premierepro` TypeScript declarations package to address some inconsistencies or improve and clarify how to use various classes and APIs. We’ll continue reviewing these and working to make sure these are as accurate as possible.

- [`ComponentParam.getValueAtTime()`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/componentparam#getvalueattime)'s return value has been better clarified as to its actual runtime values/types. In particular Point (`PointF`)-related values are actually returned as an `[x, y]` array “tuple”. Other supported values are returned as scalars (number, boolean, string).

- [`Keyframe`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/keyframe)’s and [`PointKeyframe`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/pointkeyframe)’s `value` property has been better qualified in terms of its expected values/types. In particular the TypeScript declaration has been further split into getter and setter accessor declarations to highlight the difference in getting values from each Keyframe class and setting values. You can see this most clearly with `PointKeyframe`.

- [`Project.getSequence()`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/project#getsequence) is now correctly documented as being an _asynchronous_ function, returning `Promise<Sequence | null>` rather than suggesting it always _synchronously_ returns a `Sequence` instance.

- [`ProjectItem.type`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/projectitem#properties), [`ClipProjectItem.type`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/clipprojectitem#properties), and [`FolderItem.type`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/folderitem#properties) more specifically use the newly added `Constants.ProjectItemType` enumeration to help identify what type values are present for each class rather than using `number` more generically.

- [`TrackItemSelection.createEmptySelection()`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/trackitemselection#createemptyselection) better documents lifetime and scope limitations with the empty `TrackItemSelection` object provided to the callback function. We’ve similarly added a new ESLint rule to the `@adobe/eslint-plugin-premierepro` plugin to help identify incorrect usage through static analysis checks.

- [`Transcript.transcribeClipProjectItem()`](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/transcript#transcribeclipprojectitem)'s options have been corrected to accept an optional `language` property rather than `languageCode`. How this works between transcription default settings and language auto-detection has been further clarified in the method’s description.

---

<div class="post-metadata">

**Author:** ![bbb\_999](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/bbb_999/32/4247_2.png) [@bbb\_999](https://forums.creativeclouddeveloper.com/u/bbb_999)\
**Post date:** [November 12, 2026, 4:08pm UTC](https://forums.creativeclouddeveloper.com/t/premiere-27-0-api-updates/12436/2 "2026-11-12T16:08:35Z")

</div>

Closed on November 12, 2026, 4:08pm UTC


