Norbert, hi -
Our use case is a QR code with a customer logo inserted. So we are relying on both the uploadImage and custom QR APIs. It all works fine.
The logo may change but not often. We found that we can re-use the object URL (eg- “f2bf0c09b17cb9760d59cd7fda61813f5e4c9cbd.png” for a particular logo uploaded previously and avoid calling the uploadImage API ever time we need a new QR code.
We also noticed that if we call uploadImage API repeatedly with the same image, the object URL returned is the same each time. This leads me to two questions:
Are we incrementing the billing object for each call to POST uploadImage, even if the URL returned is the same?
If so, is there any way for us to test whether we really need to call uploadImage. For example, can we detect whether the object URL (eg- “f2bf0c09b17cb9760d59cd7fda61813f5e4c9cbd.png” is valid and still exists on the server?
Join in the discussion - add comment below: