コミュニティアチーブメントバーを展開する。

Don’t miss the Workfront AMA: System Smarts & Strategic Starts! Ask your questions about keeping Workfront running smoothly, planning enhancements, reporting, or adoption, and get practical insights from Adobe experts.

Which Adobe Workfront API Version Do You Use (and Why?)

Avatar

Community Advisor

Hi Folks,

 

Today, Adobe Workfront shared this announcement upon login:

 

Doug_Den_Hoed__AtAppStore_1-1757516390665.png

 

We first learned of the upcoming change a couple of weeks ago (then, cited less precisely as "Sept 2025"), so have been working furiously to upgrade all of our solutions, and were delighted to make a similar announcement today in response:

 

Doug_Den_Hoed__AtAppStore_0-1757516339932.png

 

As Workront's oldest partner, we had vestigial references going back to API v2.0 all the way up to current (v20.0), and as we tackled this upgrade, had to decide whether to:

 

  • use the "Latest" API by NOT specifying a version and instead "roll with it" whenever the official Latest version changes (so less maintenance, but more risk), or
  • use the specific "v20.0" latest version to "lock in" that functionality, recognizing that someday the code will need to then be upgraded (deferred maintenance)

We decided to go with the latter, and have teed up our tech stack to make future such transitions less onerous, but I am curious what others are doing.

 

Which version(s) of the Workfront API are you using, and why?

 

Regards,

Doug

 

cc: @Doug_Den_Hoed__AtAppStore note to self...

 

 

3 返信

Avatar

Level 1

Thank you for the additional information and your consistently exceptional customer service, Doug. My team relies on you and AtAppStore to keep us running smoothly in our fast-paced marketing environment, and we truly appreciate your support.

Avatar

Level 2

How can I view which API version I'm currently using? Is it in the Workfront Settings?

Avatar

Community Advisor

 

Hi @BrittanyGarrett,

 

To present data via the User Interface, Workfront itself uses "api-internal" (mostly), which has the most broad and latest version of the API. If you're just using that UI, then no worries -- Adobe tests and ensures that all of their released functionality then Just Works.

 

If you're using the API directly (as we do for our AtAppStore Solutions) or with Fusion, other API's come into play. Technically, you could use api-internal, but since it is extremely similar (if not identical) to "api-unsupported" (which Adobe created to stress the "unsupported" part), the latter is recommended...but only when the functionality you need is NOT provided via an officially "versioned" API. At the moment, "v20.0" is the latest and most current such versioned API, with v21.0 (and several earlier editions) also available.

 

With that context, I invite you to learn more here.

 

Regards,

Doug