Is the issue happening for the API which you created for very first time ? Are its happening for the existing API . if so is there any changes to endpoint recently ?
Did you promoted this API via manual Import or using continuous Integration.
Try to download the compare the API Package from problematic environment with your lower environment ( working ). Do you see was there is any mismatch with the Gateway endpoint
Set your problematic environment API Gateway logs to debug and try to analysis the logs during the issue and after deactivate and activate
Find my response.
1.Is the issue happening for the API which you created for very first time ? Are its happening for the existing API . if so is there any changes to endpoint recently ? - APIs are versioned or standalone , there is no pattern as such, endpoints are same
Did you promoted this API via manual Import or using continuous Integration.- manual import
Will give try on your suggestions but meanwhile is it possible to have some suggestion, fix or work around, that can resolve it?
if there is no changes to your end point. I would request or suggestion you to verify the exported package and try to verify the json file. Do you see any “/” is appended in your endpoint.
Also enable the debug log and test the service before export from lower environment and after importing the same package to higher environment.
if you don’t see any progress in your finding , I would suggest you to create support ticket for temp work around fix. Maybe your endpoint might malfunctioned.
Work around is already you doing by enabling and disabling the API.