Is there a way to not cache the result of the event segmentation API?

Hello Jeong,

Based on the information available, it appears that the caching of API responses is a feature of Amplitude's system. This is done to ensure efficient processing of requests, especially those that may have a longer duration. The cached results are typically refreshed after a certain period, which can sometimes lead to the same results being returned for multiple queries within that period.

Unfortunately, there is no parameter or header that can be submitted with the request to bypass this caching feature or to control the cache arbitrarily. The system is designed this way to manage the load and ensure optimal performance.

However, if you're experiencing significant issues with this, I would recommend providing feedback directly to our product team via the Amplitude widget at the bottom right corner on the UI > Give Feedback. A detailed description of your use case and how you visualize utilization of the platform without the caching behavior would help our Product team understand the importance of the request better.

I hope this information is helpful. Let me know if you have any other questions.

Best Regards,

Jacenda


P.S. Checkout upcoming events and user meetups on our events page.