In the AWS API-Gateway service, what does API with HTTP proxy integration and API with HTTP non-proxy integration mean?

I am trying to understand the practical concept of the meaning of API with HTTP proxy integrationand API with HTPP non-proxy integration. The Official AWS documentation explains how to create these two types of APIs but doesn't make it very clear what the practical difference between these two approaches is. As far as I could understand, the approach with proxy integration would serve to access all end-points using only a single end-point passing a variable that it would serve as an indicator of the required end-point. In non-proxy integration the end-point should be explicitly written to the URL.

Could anyone explain better?

Author: zwitterion, 2020-04-22