Currently, there is a known issue with the API Manager's "Response Caching" feature. This feature can be turned on by API publishers in the third step ("Manage") of the publishing process. The caching seems to modify the structure of the response data, this can lead to unexpected results for consumers as structures are changing seemingly at random. Currently, the extent of the problem is not fully understood. This article will be updated as the investigation continues to give more detail into what the exact issue is, what causes it, and how to fix it.
 

Effects

  • Receiving different response data structures seemingly at random when the response data should be the same
     

Workarounds

Currently there is no known workaround to this issue. In the meantime, it is suggested that API publishers disable this feature completely until the problem is more fully understood. The feature can be disabled in the third step ("Manage") of the publishing process for each individual API.

 

If you have any further questions, please get in touch with one of the API Manager team members.