Does the quality image transformation parameter in a url count as an API call?

Follow

Jacob David Cunningham

• January 04, 2017 02:13
• Edited

So you've got a known photo source

http://res.cloudinary.com/name/image/upload/#######/file.jpg

and you add the quality parameter to it like

http://res.cloudinary.com/name/image/upload/q_60/#######/file.jpg

Does that now count as an API call or not?

0

• 

  Jacob David Cunningham

  • January 04, 2017 02:18

  From this article here, it doesn't seem like the quality request counts as an API call?

  https://support.cloudinary.com/hc/en-us/articles/202520892-Are-Cloudinary-APIs-limited-

  0

  Comment actions Permalink
• 

  Jacob David Cunningham

  • January 04, 2017 02:36

  I tested it side by side, it does not affect it. Not sure why that was hard to understand, and you can server side dynamically build your urls and insert that quality parameter.

  0

  Comment actions Permalink
• 

  Ido

  • January 05, 2017 09:10
  • Edited

  Hi Jacob,

  Let me try to explain because I think that there is a small mix-up.

  Our API for uploads, transformation, and delivery is not restricted. Our admin API is restricted to 500 calls/hour for our free plan and 2000 calls/hour for our paid plans.

  I think that what you mean by adding the "q_60" flag is our transformation quota.
  We count a transformation usage only on the first time it was used to create a new derivative image. The next time the image will be called with that transformation it would not count as another transformation.

  
  So the first time you call "http://res.cloudinary.com/name/image/upload/q_60/#######/file.jpg" it would count as a transformation, but all subsequent calls would not count towards your transformation quota.
  You can read more about our quotas here

  Of course, each transformation is performed by performing a call to our API but this is transparent to our users(when using our SDKs), and like I said earlier, that API is not restricted.

  I hope this clears things out.

  0

  Comment actions Permalink
• 

  Jacob David Cunningham

  • January 04, 2017 22:27
  • Edited

  Hi, thank you for your response. I Don't know if you'll be notified of mine, I don't see a respond/reply button by your post.

  So for every photo that I call that quality transformation on it will count at least once so my question of batch (I modified the original question so maybe this question wasn't apparent/seen) quality call under a single API call, that's not going to happen right?
  
  By that I mean for example I can grab all the photos under a specific parent folder under 1 API call, but I couldn't have all those URLs with the same quality parameter under 1 API call.

   

  Am I still not getting this? That qualtiy 60% parameter q_60, if I call that on file-1.jpg, would calling that on file2.jpg count as a new API call or not?

   

  I will read through that quota link you posted.

   

  Thanks

  0

  Comment actions Permalink
• 

  Ido

  • January 05, 2017 09:19

  Hi again Jacob,

  The answer to your question is Yes.

  If you call the "q_60" parameter on `http://res.cloudinary.com/name/image/upload/#######/file-1.jpg` and then on `http://res.cloudinary.com/name/image/upload/#######/file-2.jpg` it would count as two transformations.

  This would create the below two resources. If you call these two resources again it would not count as a transformation since they were already created in the past. The transformation is counted only the first time it creates a derived resource.

  http://res.cloudinary.com/name/image/upload/q_60/#######/file-1.jpg
  http://res.cloudinary.com/name/image/upload/q_60/#######/file-2.jpg

  
  Hope this helps in clarifying

   

  0

  Comment actions Permalink
• 

  Jacob David Cunningham

  • January 05, 2017 16:22

  Thanks a lot for the support.

   

   

  0

  Comment actions Permalink

Please sign in to leave a comment.