Workfront

lgaertner · 6/27/23

Hello,

I would like to download the binary of a document via the API to get a blob object.

Is this somehow possible? I cannot find the corresponding information using the API-explorer.

I know, that I can retrieve the field downloadURL, but using this requires to be logged in to Workfront.

Thanks in advance.

Regards

Lars

ChrisStephens · 6/27/23

That's what you have to do. You have to get the download url, and then download it with that url, and both of those require an API key or a session ID.

View solution in original post

ChrisStephens · 6/27/23

That's what you have to do. You have to get the download url, and then download it with that url, and both of those require an API key or a session ID.

RahulMohan · 3/13/24

How can I get the file extension in the endpoint - /attask/api/v17.0/document/search?projectID=xxxxxxxxx&fields=folders,downloadURL . I tried adding fileType, but I'm getting below message.

"field 'fileType' is not available"
Could you please help?

ChrisStephens · 3/13/24

The file Type parameter is on the version object, so if you include currentVersion:ext, that should give it to you.

RahulMohan · 3/13/24

Thanks a ton!

CarlSt3 · 6/17/24

Hey Chris,

This information has be quite useful, however curious how to navigate the Download URL call returning the HTML webpage vs. downloading the binary. The API Key authenticates, but does returns the HTML page. Any thoughts?

ChrisStephens · 1/12/26

So since this thread still gets random replies and likes, I'll go ahead and post an update here. You can now generate a pre-signed URL for a file and just download files with that pre-signed URL instead of needing a session ID. The previously mentioned method still works, there's just now an alternative.

williamg9967703 · 1/13/26

Hi Chris,
Is there any documentation for this?
I have a similar scenario where I need to download assets and move them to azure blob storage.

I have attempted to use adobe IMS, but it seems the developer user isnt granted access to file information in workfront.
We are currently using a static refresh token. We have a vmss, and rotating the refresh token is too complex for this scenario.
There is also the option of using the workfront OAuth integration but that leads us to having to manage certs, which we are trying to eliminate.

ChrisStephens · 1/14/26

You have to be able to make an authenticated call to the document end-point, so provided you can do that it's the "getTemporaryCloudURL" command listed under documents. You provide the document version ID you want a URL for, as well as a TTL for it, and then you get a pre-signed S3 download link.

jshaw4 · 4/2/24

I am also having a problem downloading a document. I am providing an apiKey (I've tried in both $body and $header) in a CURL command through Powershell.

The $url variable contains something like this:
https://<mycompany>.my.workfront.com/internal/document/download?ID=abc123456def123456
$downloadResponse = Curl -Uri $url -Header $header -Body $body -OutFile $downloadPath

All I am getting back is a 4k file, starting with this:

<p>

<strong>Note:</strong> Since your browser does not support JavaScript,

you must press the Continue button once to proceed.

</p>

</noscript>

DaniloRa1 · 7/18/24

Having the exact same error. If i open the provided URL in my browser it downloads just fine; but trying to do it programmatically produces an error.

Were you able to solve the issue?

RichardPe3 · 1/17/25

The SessionID needs to be added either as a parameter in the download URL (&sessionID=) or the header (sessionID:''). SessionID can be retrieved from ..attask/api/v19.0/session

OmprakashKu2 · 2/24/25

I'm having the same error any one help please!

RichardPe3 · 2/25/25

Have you added the sessionID to you download request?

HumanityLabsWo · 11/14/25

Hi @jshaw4 - were you able to get download working? I tried to generate the session based on the documentation `attask/api/v21.0/session` and that call failed with AuthenticationException.

Thanks,

Chinh

HumanityLabsWo · 11/19/25

This is resolved. Our client had to regenerate a different API key for the user. Once that happened, the session endpoint worked. Added the sessionID (along the APIKey) to the downloadURL (which should be

https://<your_domain>.my.workfront.com/{downloadURL}). That should work.

Workfront

Download document using the API

Learn

Documentation

Events

Community

Support

Resources

Adobe account

Adobe