posted an update

Using the destination parameter while calling the API is no longer needed, it is now automated (Many thanks to Claire Froelich for pointing this out). Follow the instructions in the "How to test this out" section of the description.

With no automation in place for the destination parameter, since visualization metadata is stored on Google Cloud Storage, if two requests use the same destination (also serves as a unique ID) they got cached results (https://cloud.google.com/storage/docs/caching) not allowing people to use their own images very easily.

Log in or sign up for Devpost to join the conversation.