Hey,

Came across a situation where we retrieve an image from query search (reponse_group=image_details) and for some of them (user-selected) we want to request better quality images (response_group=high_resolution).

How could this be done using only the response of 1st example since it doesn't return hash_id attribute and searching by database id (ID) is not sufficient?

I'm afraid, you cannot combine these reposnes. We deliberate do not offer this feature. And don't try to combine image details with hi-res images through multiple requests. This might get your API key locked.

- Simon

I guess I am trying to do the same thing. If we cannot retrieve high_resolution images and details then how are we supposed to do searches and then get the image. I dont understand why they are disconnected.

In order to cache the searches and not Hotlink to your images I need to download the image into my system. With that I need the tags which only come from the image_details and need the high_resolution images. You seem to be telling me I cannot get both for the same image or I will be suspended.

Can you verify I understand correctly?

Just read me response above again. In short: no, you cannot get both, if and id_hash. If you try to find a way around this restriction, your API key will get locked.

I don't mean to be a pain but can you explain why? This makes the system very hard to use for my use case. Can we talk about alternatives?

Technically, it's actually not a problem. However, only "big players" like Adobe do have access to these API features. If your application is expected to play an important role and is likely to attract lots and lots of users, please let us know more by email. Otherwise, I'm afraid, you'll have to work with the API as it is.

- Simon

Hi,

I understand you don't want to add tags in high resolution lists and that we shouldn't try to merge details and hi-res.

Howerever, this makes more difficult to offer smooth experience for users who want too search by tags : this need another internet query with "&q=some+keyword" instead of having parsing within a loaded tag list. Furthermore, this adds requests to servers.

Can we hope a policy change about that in the future?

Another question (just because i'm curious), I've tried to combine both lists before reading this thread, and I've noticed that each query returned a different list, why?

Thank you for your answers

devex, in the near future you cannot expect this to change. Maybe some day later ...

It doesn't make sense to me what you're saying about the user experience. You can let your users search for keywords and they get correct results.

Your last question is basically answered by yourself: We frown upon combining tags with full res images through the API; you tried and had difficulties ... The difficulties you had were intended ;-)

- Simon

I'm sure, they could get the correct answer! But, not all people have a Wi-Fi connection on everywhere nor (worst) have a 4G access, especially in some countries. So, that why I've asked, one time connection, is always better.

However, thank you for your answer, and I'll look forward some day later to have tags with hi-res ;-)