Confusion in usage and documentation of query parameters for transactions api in v5

[cchighman]

I'm not really sure of the use case and decision behind making the transactions API do a GET operation with a POST call. Provided two layers of parameters, those for use in the body and others for use as query parameters further adds confusion since POST requests traditionally do not use query parameters. To illustrate how its easy to be confused, in the below screenshot you will see that I have included the query parameters for "ignoreChecks" yet the API still informed me I dont have enough for the transaction. This was because, by default, I put the "ignoreChecks" parameter in the body payload as well and forgot about it. If you include the ignoreChecks parameter in both the querystring and body, it will no longer consider the fact its included in the querystring. This is a bug and has room for improvement.