Skip to main content
A
autumn_records
Participating Frequently
January 12, 2023
Question

Creative Cloud Assets API issue

  • January 12, 2023
  • 4 replies
  • 1434 views

Hello Everyone,

 

I am having some problems in using the API.
 
1. I am trying to get the Creative Cloud Assets' data using API. And I am able to get the basic info about the assets using {{baseUrl}}/api/v1/libraries/{{library_id}}/elements?selector=default.
 
However, to get the description, I need to use Selector = details. And I got 401 error. Do I need additional scope or do I need to add a certain API to my application?
 
2. The documentation on how to update an element is incomplete it seems. The path below is supposed to update the elements. However the documentation just says you have to pass string of element ids. What do I need to do to update a specific field like description or name of an element?

https://cc-libraries.adobe.io/api/v1/libraries/{libraryId}/elements/metadata

This topic has been closed for replies.

4 replies

A
autumn_recordsAuthor
Participating Frequently
May 4, 2023

I didn't really need it for a month or two. Now I came back to test it again. And it's the same error.

As you can see using openid, I can easily authenticate. However, with cc_files, it fails

O
Adobe Employee
Owen24979797nzzf
Adobe Employee
February 24, 2023

Hello @autumn_records, I have finally heard back regarding the 401 error responses.

 

According to the team's logs, they are saying that sometimes your user account isn't always being authenticated with the correct scopes.  Can you make sure you are always retrieving an auth token with the scopes listed here:

 

https://developer.adobe.com/creative-cloud-libraries/docs/integrate/setup/oauth/

 

openid,creative_sdk,profile,address,AdobeID,email,cc_files,cc_libraries

Please let me know if you continue to see 401s when authenticating with these scopes.

A
autumn_recordsAuthor
Participating Frequently
March 9, 2023

cc_files, cc_libraries scopes are needed to do this, I understand that.
But the problem is I can authenticate anything with those scopes. I will add screenshots or video

 

A
autumn_recordsAuthor
Participating Frequently
May 4, 2023

O
Adobe Employee
Owen24979797nzzf
Adobe Employee
January 18, 2023

Hello,

 

The team I contacted about the 401 said it had resolved and you should be able to make that query without issue. Please let me know if you have further issues with libraries.

 

Thanks!
Owen

A
autumn_recordsAuthor
Participating Frequently
January 29, 2023

Its still the same issue. When I try to authorize using scope cc_files, I get access denied.

O
Adobe Employee
Owen24979797nzzf
Adobe Employee
January 17, 2023

Hello!

 

Sorry you having issues with the libraries API. For the first issue are you able to provide a request id of the failing request? This would be in the response from the API in a header:

 

x-request-id

 

 I should be able to track down why this would fail.

 

For the second issue can you provide a link to the documentation that doesn't contain the update element request body? That should definitely be there. For me a working cURL request to update an element:

 

 

curl --location --request PUT '/api/v1/libraries/<libraryId>/elements/metadata' \
--header 'Authorization: Bearer <token>' \
--header 'x-api-key: CCXWeb1' \
--header 'Content-Type: application/json' \
--data-raw '{
    "elements": [{
    	"id": "<elementId>",
        "name": "new name",
        "description": "new description"
    }]
}'

 

O
Adobe Employee
Owen24979797nzzf
Adobe Employee
January 18, 2023

We were able to track down your request in the logs for the first issue and can see an error and are investigating. I will respond with further information as soon as I know more, thanks!

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices