API uses a POST call as a GET because the JSON query is too long; how to configure with call template

Hi all,

I am currently trying to configure an API in the shape of a call template as a first test. However, even though the request is a GET, the API developers chose to configure it as a POST because the URL gets too long if the query is written as a GET.

This means the API uses a body to send a query and to return the results.

In this context, what I would like to do is POST the BvDID (the ORBIS equivalent of KvK) to the ‘where’ query to GET the ‘select’ data that gets produced after I send the information. I have read in another post that you can POST data using a data definition, only I do not understand how the {“WHERE”: [“”], “SELECT” [“”] } part of the JSON can be implemented. To me, it seems like I can only POST the contents of the ‘where’ using the data definition.

So my question is: how can I send along the whole query in the JSON using a call template?