[Infra] Investigate API Endpoints improvements and replacing POST with GET

[jennypavlova]

We want to improve the infra APIs and investigate different ways to do that. One thing we want to change is to convert all POST endpoints that are used to fetch data to GET.

Benefits are:

• RESTful API conventions: Elasticsearch follows the RESTful API conventions, which typically use GET requests for queries. Deviating from these conventions may make your API less intuitive and harder to understand for other developers who are familiar with RESTful APIs.
• Caching and performance: GET requests in Elasticsearch are often cached by proxies, which can improve performance. In contrast, POST requests are typically not cached, which may impact performance if the same query is executed frequently.

Concerns: If we use GET request the limit we have in the length is 2,048 characters. Moving the properties we have in the request body to the URL can exceed this limit in case of a long list of filters so we need to be careful.

AC:

• Investigate if we can covert API endpoint from POST to GET
• Test with different params and a long list of filters
• When/If possible covert API endpoint from POST to GET
• Get our APIs closer to our guidelines recommendations.

[elasticmachine]

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

[crespocarlos]

This would also get our APIs closer to our guidelines recommendations.

[jennypavlova]

This would also get our APIs closer to our guidelines recommendations.

Thanks @crespocarlos I added that to the AC

[smith]

Removing from refining into backlog.