Question Concerning API Usage and Assets
As you all know Kentico Cloud charges based on API usage. We have a site which is using the Delivery API to serve content to our visitors. My concern is in regards to Content Models with Asset Fields. Suppose I have a "Home_Page" Content Model which has 3 Asset content elements (in our case these are images). When a visitor lands on our sites Home Page I request a "Home_Page" Content Item which is (1) API call, the Delivery Item Response object is returned with the Asset elements. These asset elements have a URL value, I set source of the images on the home page to the URL values.
When the page renders in the client's browser am I charged an additional (3) API calls to fetch the images from Kentico Cloud? If the answer is yes, this is a problem considering the asset URLS point directly to Kentico cloud (bypassing the cached delivery client I have in place). Additionally if one of my visitors (or something like Google Images) hot links directly to one of my assets I will be charged every time the image is viewed, ultimately taking this out of my control.
If fetching Assets from Kentico cloud counts as an API call it become very difficult to predict pricing for my clients based on their current site traffic. I can put caching in place for fetching the Content Items, however, the images are out of our control.
Any idea if this is true? Or if Asset downloads do NOT count against your API total since they are not actually using the Delivery API?