In general: GET can have caching, POST should not. However, if you are dealing with internal only systems, it doesn't really matter. Browsers and some tools hav

In general: GET can have caching, POST should not. However, if you are dealing with internal only systems, it doesn't really matter. Browsers and some tools have optimizations and expectations around what can be done with different HTTP verbs. Maybe your load balancer could see the same GET request and serve a cached value (as long as it counts the body in its caching logic). If you are not hoping to take advantage of GET caching, just stick with a POST.