Due to security issues in our organization, it’s not allowed to transfer fields which not defined on the original swagger definition. The process worked fine until today on about 12:00PM.
on 12:00 the response suddenly return a JSON with additional field. the field is “show_join_info” and it’s value is false. due to that addition, all our requests was blocked by our API Gateway.
My questions are:
How can I prevent this issue from happening again? I don’t want any changes without aknowledge us first.
Where can I see the most updated responses’ schema?
If this kind of problem happens, how can rollback?
which settings affects the “show_join_info” field?
Hi @uzi.mishan
Thanks for reaching out to us!
Sorry to hear that you are having issues with your integration.
I just looked into our Docs, and I do not see the “show_join_info” field in the response, but also looked at some API calls that I made on friday and this field was already in the response.
I will go ahead and (1) reach out to the Docs team so they can update the response’s schema and (2) I will look internally to get information on when this field was first introduced and to learn more about this setting.
Here is a link to our Changelog where you can keep and eye and follow to learn more about upcoming changes: