I'm currently working on a Database Proxy API Project I cooked up (essentially creating a way I so we could query our different MySQL and Oracle databases using

I'm currently working on a Database Proxy API Project I cooked up (essentially creating a way I so we could query our different MySQL and Oracle databases using a RESTful API) and it makes sense for me (from the RESTful perspective) to use a GET request to send the query. However, I know that the request body (a JSON string or a JSON array that could contain one or more queries, along with one or more different decryption keys allowing the server-side to retrieve the connection details that are encrypted on the server) could be quite long (we have some massive SQL queries that get used elsewhere and could potentially be used with this new API once it's available) and I also didn't like the idea of some of the more sensitive information being in the URL, so I decided to implement it as a POST request instead of a GET. It feels wrong (again from the RESTful perspective since I'd like my API to be fully RESTful) but from a user point of view I know I'm making the right decision. If anybody has better ideas though, please let me know!