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

[Doug_Den_Hoed__AtAppStore]

Hi Folks,

Today, Adobe Workfront shared this announcement upon login:

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:

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...

[EileenW]

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.

[BrittanyGarrett]

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

[Doug_Den_Hoed__AtAppStore]

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

[Prapoorna]

Hello Doug, 

We are currently using Workfront API version v12 and I understand that this version is being deprecated. As we plan to upgrade to the latest API version, I wanted to confirm: can we continue using our existing API key with the updated version or will we need to generate a new one?

Appreciate your guidance on this.

[Doug_Den_Hoed__AtAppStore]

Hi @Prapoorna,

API Keys have their own (independent) lifespan, so yes - as long as it has not expired - you can continue to use your existing API Keys against any version of the API at a point in time.

Regards,

Doug

[kautuk_sahni]

@Doug_Den_Hoed__AtAppStore Just checking in! Were you able to get this resolved? If you found your own solution, sharing the details would be a big help to others who might face the same issue later on. And if one of the replies here helped, whether it fully solved the problem or simply pointed you in the right direction, marking it as accepted makes it much easier for future readers to find. Thanks again for helping close the loop and contributing to the community!

[TechAt]

Hi @kautuk_sahni,

Thanks for your nudge. Although the subject ends with a question mark, this post (as with many of my favorites) -- hah! as Laruen C is explaining on our webinar as I type this -- is intended to be a discussion for awareness, so I have moved this accordingly under Discussions.

So no right answer...but no wrong ones, either!

Regards,
Doug