Skip to main content
Participant
July 18, 2023
Answered

Photoshop API "output.href" need for explanations

  • July 18, 2023
  • 1 reply
  • 1404 views

Hi,

 

I'm trying to implement the photoshop api and more precisely the "remove background" endpoint.

I'm still doing test with Postman, and I don't understand, or I didn't found the documentation related to the output url.
We're using custom solutions (PHP/Symfony) and don't want to go through AWS, Google drive, Azure or Dropbox to get the result.

I've got a web server, with an url open in POST/PUT where I just log the complete request (trying to understand what the api is really returning), 

 

With postman, I use the endpoint "https://image.adobe.io/sensei/cutout" to create my job (as explained in https://developer.adobe.com/photoshop/photoshop-api-docs/api). 

I use my logging url as output.href string value. As for the 'storage' value, is "external" since it's not any of the solutions cited above.

 

When I check the status of the job, I was first getting certificate errors.
-> Updated my server with a valid certificate, problem solved.

Now my job have an other error : 403, "Unable to upload the outputs", "AuthForbidden".
But I didn't put any authentication method on my url. And when I check the logs, nothing has tried to even connect to this url. Why is the API returning an auth error whitout even trying to access my url ?

 

Is there a documentation for this "output" href ? 

This topic has been closed for replies.
Correct answer Archy P

Hi there! 

 

Sorry to hear you're having some issues with the API. Here is the link to our documentation where you can learn more about how storage works. Since the API requires permissions to read and write to the URL we recommend using presigned urls with the storage solutions noted in the documentation. In theory you could use a different storage solution but do not have any documentation on how to accomplish this as its not fully supported yet. 

 

Best, 

1 reply

Archy P
Adobe Employee
Archy PCorrect answer
Adobe Employee
July 18, 2023

Hi there! 

 

Sorry to hear you're having some issues with the API. Here is the link to our documentation where you can learn more about how storage works. Since the API requires permissions to read and write to the URL we recommend using presigned urls with the storage solutions noted in the documentation. In theory you could use a different storage solution but do not have any documentation on how to accomplish this as its not fully supported yet. 

 

Best, 

LuminRabbit
Inspiring
August 20, 2023

Hi there @Archy P 

 

The link to the documentation does say The Photoshop API works with any public or signed url.

I believe Im running into a similar issue with the Get status of a job and a different call.

 

The problem with signed url is you have to pay for another storage provider (on top of one you may already be using) and then well be paying $0.15 per API call along with other call fees not associsated with adobe, being able to use a public soltuion where user authorizations are handled on the developer side sure would make things less painfull.

LuminRabbit
Inspiring
August 20, 2023

Please disregard my previous port I went with Dropbox and all is working fine.