I'm building a simple app that is a client web application and an API behind it. I'm combining two third-party APIs, one needs to be called from my client application (for ease of authentication) and one needs to be called by the server.
The data I receive from my first API is a list of strings - it will be between 0 and 150 items long, each string is an unknown length. Each one of these items needs to be passed to my server - either as individual elements (preferred) or as a serialised string. My endpoint will always return a single object, regardless of how many items are passed to it.
What is the most semantic way of passing this data to my API?
It's not really a GET request as the returned object is dynamic, and I'm concerned about the URL length limits (discussed here) given that I don't know what these strings will look like.
POST also feels incorrect as I'm not going to storing what is sent to me, though this would allow me to send the data in the body of the request and not worry about the size.
Perhaps I shouldn't worry so much about semantics and just do what works, but I'm interested in opinions on the best, or 'proper', way to design my API here.